sandbox_config
Enable/disable container isolation for guest or host tasks. Configure resource limits and network mode. Changes are persisted to config file.
This record as markdown: /tools/io-github-kivanccakmak-yaver/sandbox-config.md
What sandbox_config does on Yaver
AI agents use sandbox_config to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
cpu_limit | string | — | CPU limit (e.g. '2.0') |
read_only | boolean | — | Read-only root filesystem (writes only to /workspace, /tmp) |
memory_limit | string | — | Memory limit (e.g. '4g') |
network_mode | string | — | Network mode: 'host', 'bridge', or 'none' |
containerize_host | boolean | — | Run host tasks in Docker containers |
containerize_guests | boolean | — | Run guest tasks in Docker containers |
Parameters from the server's own tool schema.
Why sandbox_config is rated Medium
This tool modifies security-relevant configuration (container isolation, network mode, resource limits) and persists those changes to a config file. While reversible in principle, misconfiguration could disable container isolation or open network access, making the blast radius high. It is a Write operation as it creates/modifies configuration data rather than executing commands or deleting data.
From the tool's definition Enable/disable container isolation for guest or host tasks. Configure resource limits and network mode. Changes are persisted to config file.
Attacks that exploit this kind of access
The rule that runs sandbox_config safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sandbox_config, this is the rule to start with:
sandbox_config 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 Yaver, apply this rule, and every sandbox_config call is checked against it from then on.
Questions about sandbox_config
Enable/disable container isolation for guest or host tasks. Configure resource limits and network mode. Changes are persisted to config file. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
sandbox_config accepts 6 parameters: cpu_limit, read_only, memory_limit, network_mode, containerize_host, containerize_guests. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for sandbox_config: 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 Yaver. Nothing to install.
sandbox_config 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 sandbox_config 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 sandbox_config. 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.
sandbox_config is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue