Get status of current or recent task execution.
AI agents call get_execution_status to retrieve information from Claude Code Control MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about previously initiated tasks. It has no side effects—it only reads and reports execution state. While the server as a whole supports Execute and Write operations (execute_code_task, modify_files, run_commands), this specific tool is a passive status checker that falls clearly into the Read category with low risk.
From the tool's definition Tool name 'get_execution_status' and description 'Get status of current or recent task execution' indicate a query/retrieval operation that returns status information without modifying or executing anything.
Attacks that exploit this kind of access
Get status of current or recent task execution. It is categorised as a Read tool in the Claude Code Control MCP MCP Server, which means it retrieves data without modifying state.
Register the Claude Code Control MCP server in PolicyLayer and add a rule for get_execution_status: 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 Claude Code Control MCP. Nothing to install.
get_execution_status 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_status 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_status. 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_status is provided by the Claude Code Control MCP server (marc-shade/claude-code-control-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 →