New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

start_sandbox_execution

Start a new sandboxed execution for an Agent. Freezes the policy snapshot and returns the execution record + policy envelope.

SERVERTodo for AI MCP Server SOURCEtodo-for-ai/todo-for-ai-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/todo-for-ai-todo-for-ai-mcp/start-sandbox-execution.md

What start_sandbox_execution does on Todo for AI MCP Server

AI agents invoke start_sandbox_execution to trigger actions in Todo for AI MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why start_sandbox_execution is rated High

start_sandbox_execution triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Questions about start_sandbox_execution

What does the start_sandbox_execution tool do? +

Start a new sandboxed execution for an Agent. Freezes the policy snapshot and returns the execution record + policy envelope. It is categorised as a Execute tool in the Todo for AI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_sandbox_execution? +

Register the Todo for AI MCP Server MCP server in PolicyLayer and add a rule for start_sandbox_execution: 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 Todo for AI MCP Server. Nothing to install.

What risk level is start_sandbox_execution? +

start_sandbox_execution is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_sandbox_execution? +

Yes. Add a rate_limit block to the start_sandbox_execution 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.

How do I block start_sandbox_execution completely? +

Set action: deny in the PolicyLayer policy for start_sandbox_execution. 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.

What MCP server provides start_sandbox_execution? +

start_sandbox_execution is provided by the Todo for AI MCP Server MCP server (todo-for-ai/todo-for-ai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Todo for AI MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Todo for AI MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.