---
sourceDocument: Brazil Enable AI
sourceDocumentLink: https://www.servicenow.com/docs/r/intelligent-experiences
Release :
- brazil
ft:locale :
- en-US
ft:publication_title :
- Brazil Enable AI
ft:clusterId :
- platai
bundleId :
- platai
workflow :
- Platform
---
# Create a sandbox rule
# Create a sandbox rule for an Arc policy {#ariaid-title1}
Release version: Brazil
Updated October 22, 2026
 2 minutes to read
Restrict the reach of ServiceNow Arc agent commands by limiting the paths, binaries, system calls, and environment variables the sandbox can use.
## Before you begin
Role required: sn_ai_governance.ai_steward and sn_app_arc.admin
## About this task
Arc runs agent commands in an isolated sandbox on the user's device. Sandbox rules add restrictions to that sandbox. They can't remove its built-in protection of credential paths and system directories.
## Procedure
1. Navigate to AllAI Control TowerHomeGovernPoliciesArc policies.
2. Select the policy you want to update.
3. Select More.
4. Select Sandbox rules.
5. Select Create sandbox rules.
If the policy already has sandbox rules, select + Add rule instead.
6. On the form, fill in the fields.
{#gov-pol-arc-create-sandbox-rule__table_sandbox_rule_fields__entry__2}
| Field | Description |
|-|-|
| Rule Name | Name that describes what the rule does, for example, Allow curl binary or Read-only /etc. |
| Rule Type | What the rule controls. Filesystem : A file or directory path in the sandbox. Binary : A program in the sandbox and the network access it gets. Syscall : A system call that programs in the sandbox can make. Environment Variable : An environment variable in the sandbox. |
| Access Mode | Access the sandbox gets to the path, binary, system call, or variable. * Read Only * Read / Write * Allow * Deny Use Read Only or Read / Write for filesystem paths, and Allow or Deny to permit or block a binary or system call. To keep agent actions from changing a path, select Deny. |
| Path / Binary / Syscall | Target of the rule. Glob patterns are supported. For a filesystem rule, enter a path such as /home/*. For a binary rule, enter the program's path such as /usr/bin/curl. For a syscall rule, enter the system call name such as ptrace. |
| Apply to UID | User ID in the sandbox the rule applies to. Leave it empty to apply the rule to every user ID. 998 is the sandbox user. Rules don't apply to root (0), which runs the sandbox's startup scripts. |
| Active | Option to enforce the rule. Selected by default. An inactive rule is left out of the policy for every policy that links it. |
| Description | Compliance reason for the rule, kept for your audit trail. |
[Table 1. New Sandbox rules side panel]
{#gov-pol-arc-create-sandbox-rule__table_sandbox_rule_fields}
7. Select Create.
## Result
The rule appears on the policy's Sandbox rules tab, and the sandbox applies it for the users the policy covers at their next policy sync.
## Example: Let the agent read a shared folder but not change it {#gov-pol-arc-create-sandbox-rule__example-read-only-folder}
Your analysts keep approved templates in a reference folder in their home directory. Arc should be able to read the templates but never edit or delete them. Create a sandbox rule with the following values:
* Rule Name: Read-only reference templates
* Rule Type: Filesystem
* Access Mode: Read Only
* Path / Binary / Syscall: /home/*/reference
* Description: Protect approved templates from agent changes.
The \* in the path matches any user's home directory, so one rule covers every analyst. Leave Apply to UID empty so the rule applies to every user ID in the sandbox except root.
## What to do next
For a worked example that protects the sandbox runtime directory with a filesystem deny rule, see [Prevent changes to sandbox files](https://www.servicenow.com/docs/access?context=prevent-changes-sandbox&version=brazil&pubname=brazil-application-development&ft:locale=en-US).
*[\>]: and then