Retrieve detailed information about a specific command execution, including status, output, execution time, and any errors. Use the execution_id returned from shell_execute.
AI agents call process_get_execution to retrieve information from MCP Shell Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries past execution results by ID. It has no side effects, modifies no data, and performs no external operations. It is purely informational, similar to a log or history lookup. The low severity reflects that exposure carries minimal risk—an agent can only read information about executions that already occurred.
From the tool's definition 'Retrieve detailed information about a specific command execution, including status, output, execution time, and any errors' — retrieves execution metadata and results without modifying or executing anything.
Attacks that exploit this kind of access
Retrieve detailed information about a specific command execution, including status, output, execution time, and any errors. Use the execution_id returned from shell_execute. It is categorised as a Read tool in the MCP Shell Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Shell Server MCP server in PolicyLayer and add a rule for process_get_execution: 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 MCP Shell Server. Nothing to install.
process_get_execution 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 process_get_execution 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 process_get_execution. 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.
process_get_execution is provided by the MCP Shell Server MCP server (mako10k/mcp-shell-server). 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 →