configure_sandbox_policy
Create or update a security policy for OpenClaw agent sessions.
This record as markdown: /tools/io-github-homenshum-nodebench/configure-sandbox-policy.md
What configure_sandbox_policy does on Nodebench
AI agents use configure_sandbox_policy to create or update resources in Nodebench, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodebench environment.
Why configure_sandbox_policy is rated Medium
This tool modifies security policies for agent sessions, which is a reversible write operation. While it affects security posture and could have broad impact if misconfigured, it does not destroy data (Destructive), move money (Financial), or execute arbitrary code (Execute).
From the tool's definition Tool description states 'Create or update a security policy' — these are write operations that modify configuration state. The term 'configure' combined with 'create or update' indicates data modification rather than retrieval or deletion.
Attacks that exploit this kind of access
The rule that runs configure_sandbox_policy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For configure_sandbox_policy, this is the rule to start with:
configure_sandbox_policy stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every configure_sandbox_policy call is checked against it from then on.
Questions about configure_sandbox_policy
Create or update a security policy for OpenClaw agent sessions. It is categorised as a Write tool in the Nodebench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nodebench MCP server in PolicyLayer and add a rule for configure_sandbox_policy: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Nodebench. Nothing to install.
configure_sandbox_policy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the configure_sandbox_policy rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for configure_sandbox_policy. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
configure_sandbox_policy is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue