trace_info

Get detailed metadata about a specific trace

Server Rr jnjaeschke/rr-mcp
Category Read
Risk class Low
Parameters 00 required

What trace_info does on Rr

AI agents call trace_info 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.

Why trace_info needs a policy

This tool queries and retrieves metadata about an existing trace in the rr debugging session. It performs a read-only operation that returns information without altering state, executing code, or performing destructive actions. The verb 'get' and passive framing ('Get detailed metadata') confirm this is a Read category tool with low severity.

From the tool's definition Tool name 'trace_info' and description 'Get detailed metadata about a specific trace' indicates retrieval of information with no modification or side effects.

Questions about trace_info

What does the trace_info tool do? +

Get detailed metadata about a specific trace. It is categorised as a Read tool in the Rr MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on trace_info? +

Register the Rr MCP server in PolicyLayer and add a rule for trace_info: 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.

What risk level is trace_info? +

trace_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit trace_info? +

Yes. Add a rate_limit block to the trace_info 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.

How do I block trace_info completely? +

Set action: deny in the PolicyLayer policy for trace_info. 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.

What MCP server provides trace_info? +

trace_info 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.