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

agent_run

Start a managed Claude agent (Claude Agent SDK loop) inside a fresh Firecracker microVM. By default the agent has Bash/Read/Write/Edit/Glob/Grep/WebFetch (interactive/session tools like Agent, AskUserQuestion, Skill, TodoWrite are denied — this is a headless VM) and full root with open internet e...

SERVEREasyBits SOURCE@easybits.cloud/mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/cloud-easybits-easybits/agent-run.md

What agent_run does on EasyBits

AI agents invoke agent_run to trigger actions in EasyBits. 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 agent_run is rated High

Executes arbitrary code with root privileges and internet access in isolated VM environment.

From the tool's definition Start managed Claude agent in Firecracker microVM, root, internet egress, Bash/Read/Write

Risk signalsAdmin/system-level operation

Questions about agent_run

What does the agent_run tool do? +

Start a managed Claude agent (Claude Agent SDK loop) inside a fresh Firecracker microVM. By default the agent has Bash/Read/Write/Edit/Glob/Grep/WebFetch (interactive/session tools like Agent, AskUserQuestion, Skill, TodoWrite are denied — this is a headless VM) and full root with open internet egress. EasyBits supplies Anthropic credentials by default (OAuth/Max-plan token preferred, API key fallback) and bills the run; switch to BYOK (Bring Your Own Key) by registering your own credential via. It is categorised as a Execute tool in the EasyBits MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on agent_run? +

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

What risk level is agent_run? +

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

Can I rate-limit agent_run? +

Yes. Add a rate_limit block to the agent_run 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 agent_run completely? +

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

agent_run is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on EasyBits, 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 EasyBits'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.