Create a git worktree-based sandbox rooted under .sandboxes/<id>.
AI agents use sandbox_create to create or update resources in Promethean OS MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Promethean OS MCP environment.
This tool creates a new git worktree, which is a reversible modification to the repository state. It does not execute arbitrary code (Execute), delete data (Destructive), or move money (Financial). While worktrees can be used as a basis for further operations, the tool itself only creates the sandbox structure.
From the tool's definition Tool name 'sandbox_create' and description indicate it 'Create[s] a git worktree-based sandbox'. Creating a new worktree is a write operation that modifies the repository structure by adding a new working directory.
Attacks that exploit this kind of access
Create a git worktree-based sandbox rooted under .sandboxes/<id>. It is categorised as a Write tool in the Promethean OS MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Promethean OS MCP server in PolicyLayer and add a rule for sandbox_create: 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 Promethean OS MCP. Nothing to install.
sandbox_create 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_create 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_create. 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_create is provided by the Promethean OS MCP server (octave-commons/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →