AI agents call trace_processes to retrieve information from Rr without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query/list operation that retrieves debugging session state. It has no side effects, does not execute code, does not modify data, and does not delete anything. The information returned is read-only diagnostic data about an already-captured trace. Severity is low because exposing process metadata from a debugging session has minimal blast radius.
From the tool's definition Tool name and description indicate it 'List[s] all processes in a trace' — a retrieval operation that returns metadata (PID, parent PID, command, exit status) without modifying or executing anything.
Attacks that exploit this kind of access
List all processes in a trace with PID, parent PID, command, and exit status. It is categorised as a Read tool in the Rr MCP Server, which means it retrieves data without modifying state.
Register the Rr MCP server in PolicyLayer and add a rule for trace_processes: 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 Rr. Nothing to install.
trace_processes 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 trace_processes 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 trace_processes. 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.
trace_processes is provided by the Rr MCP server (jnjaeschke/rr-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 →