Get the current output and status of a running or completed async command by process_id.
AI agents call get_command_output to retrieve information from Run Command MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves output and status information from an already-running or completed process. It does not start, modify, or terminate any process — it is a pure read/query operation. The slight risk is that output may contain sensitive data, but the tool itself has no side effects.
From the tool's definition 'Get the current output and status of a running or completed async command by process_id'
Attacks that exploit this kind of access
Get the current output and status of a running or completed async command by process_id. It is categorised as a Read tool in the Run Command MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Run Command MCP Server MCP server in PolicyLayer and add a rule for get_command_output: 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 Run Command MCP Server. Nothing to install.
get_command_output 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_command_output 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_command_output. 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_command_output is provided by the Run Command MCP Server MCP server (stilllovee/run-command-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 →