Get statistics about the code execution environment.
AI agents call get_execution_stats to retrieve information from Code Execution MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves statistical metadata about the execution environment without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal security risk—it merely exposes environmental telemetry that an agent could query for monitoring purposes.
From the tool's definition Tool name is 'get_execution_stats' and description states it 'Get statistics about the code execution environment.' The verb 'get' and lack of any modification language indicate a query operation.
Attacks that exploit this kind of access
Get statistics about the code execution environment. It is categorised as a Read tool in the Code Execution MCP MCP Server, which means it retrieves data without modifying state.
Register the Code Execution MCP server in PolicyLayer and add a rule for get_execution_stats: 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 Code Execution MCP. Nothing to install.
get_execution_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_execution_stats 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 get_execution_stats. 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.
get_execution_stats is provided by the Code Execution MCP server (marc-shade/code-execution-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 →