Run code in a secure E2B sandbox. Returns stdout, stderr, and any errors.
AI agents invoke run_code to trigger actions in Vending Machine. 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.
Code execution tools are classified as Execute because their effects are contingent on the code arguments provided. Although sandboxed, this does not eliminate risk; a malicious prompt could direct the agent to run code that exfiltrates data, probes the network, or performs reconnaissance.
From the tool's definition Tool description states it 'Run[s] code in a secure E2B sandbox' — the verb 'run' directly indicates arbitrary code execution. The return of stdout, stderr, and errors confirms the tool executes user-supplied or agent-directed code and surfaces its output.
Attacks that exploit this kind of access
Run code in a secure E2B sandbox. Returns stdout, stderr, and any errors. It is categorised as a Execute tool in the Vending Machine MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vending Machine MCP server in PolicyLayer and add a rule for run_code: 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 Vending Machine. Nothing to install.
run_code is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_code 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 run_code. 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.
run_code is provided by the Vending Machine MCP server (yokiidesu/vending-machine-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 →