Explain a single PID with ownership evidence, host/tool profiles, reasons, blockers, and cleanup eligibility. It never terminates processes.
AI agents call process_explain to retrieve information from Clean Process Ended without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays diagnostic information about a process (ownership evidence, profiles, reasons, blockers, eligibility). It explicitly states it never terminates processes, making it a pure read/inspection operation with no side effects.
From the tool's definition 'Explain a single PID with ownership evidence' and 'It never terminates processes'
Attacks that exploit this kind of access
Explain a single PID with ownership evidence, host/tool profiles, reasons, blockers, and cleanup eligibility. It never terminates processes. It is categorised as a Read tool in the Clean Process Ended MCP Server, which means it retrieves data without modifying state.
Register the Clean Process Ended MCP server in PolicyLayer and add a rule for process_explain: 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 Clean Process Ended. Nothing to install.
process_explain 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_explain 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_explain. 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_explain is provided by the Clean Process Ended MCP server (marcelocaporale/clean-process-ended). 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 →