AI agents call browser_perf_get_metrics to retrieve information from Browser without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries browser performance metrics without modifying any data or triggering side effects. It is purely diagnostic/observational in nature, consistent with browser_console_get and other Read-category telemetry tools on this server. The low severity reflects minimal risk even if called by an agent, as gathering performance metrics poses no direct threat to data integrity or system state.
From the tool's definition Tool name and description both indicate retrieval: 'Get runtime performance metrics' with no mutation of state. Collects diagnostic data about DOM nodes, event listeners, and JS heap—observational only.
Attacks that exploit this kind of access
Get runtime performance metrics (DOM nodes, event listeners, JS heap) (see browser_docs). It is categorised as a Read tool in the Browser MCP Server, which means it retrieves data without modifying state.
Register the Browser MCP server in PolicyLayer and add a rule for browser_perf_get_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 Browser. Nothing to install.
browser_perf_get_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 browser_perf_get_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 browser_perf_get_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.
browser_perf_get_metrics is provided by the Browser MCP server (ricardodeazambuja/browser-mcp-server). 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 →