Get comprehensive render metrics including component-level performance data and trends
AI agents call get-detailed-render-metrics to retrieve information from Debugger MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves performance metrics and monitoring data from a running React/Next.js application via Chrome DevTools integration. It is a read-only operation that gathers intelligence about render performance without modifying application state, data, or code.
From the tool's definition Tool name 'get-detailed-render-metrics' and description 'Get comprehensive render metrics including component-level performance data and trends' indicate data retrieval with no modifications.
Attacks that exploit this kind of access
Get comprehensive render metrics including component-level performance data and trends. It is categorised as a Read tool in the Debugger MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Debugger MCP Server MCP server in PolicyLayer and add a rule for get-detailed-render-metrics: 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 Debugger MCP Server. Nothing to install.
get-detailed-render-metrics 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-detailed-render-metrics 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-detailed-render-metrics. 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-detailed-render-metrics is provided by the Debugger MCP Server MCP server (phoenixrr2113/debugger-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 →