Summarize CPU/RSS impact, top blockers, and report partitions for related processes.
AI agents call resource_impact_report 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 reads and summarizes resource usage data (CPU, RSS/memory) and reports on process partitions. It performs no writes, executions, or destructive actions. The server description emphasizes 'safe inspection and dry-run cleanup', further confirming this is a read-only reporting tool. Severity is low as misuse only reveals process resource information.
From the tool's definition 'Summarize CPU/RSS impact, top blockers, and report partitions' — purely aggregates and reports metrics about related processes with no side effects
Attacks that exploit this kind of access
Summarize CPU/RSS impact, top blockers, and report partitions for related 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 resource_impact_report: 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.
resource_impact_report 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 resource_impact_report 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 resource_impact_report. 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.
resource_impact_report 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 →