code_executor · AgentSpawn MCP: Risk & Policy

WHAT IT DOES

What code_executor does on AgentSpawnMCP

AI agents invoke code_executor to trigger actions in AgentSpawnMCP. 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 IT NEEDS A POLICY

Why code_executor needs a policy

This tool executes code, which can trigger external operations, resource consumption, network calls, or system modifications. While the description mentions 'calculations and analysis' (suggesting benign use cases), the capability to execute arbitrary code places it in the Execute category.

From the tool's definition Tool is named 'code_executor' and description states 'Execute code for calculations and analysis.' The verb 'Execute' directly indicates the tool runs code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

code_executor Rate-limited

code_executor stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "code_executor": {
      "limits": [
        {
          "counter": "code_executor_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches AgentSpawnMCP, so you can run agents against it safely.

FAQ

Questions about code_executor

What does the code_executor tool do? +

Execute code for calculations and analysis. It is categorised as a Execute tool in the AgentSpawnMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on code_executor? +

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

What risk level is code_executor? +

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

Can I rate-limit code_executor? +

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

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

code_executor is provided by the AgentSpawn MCP server (sandsaber/agentspawnmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.