High Risk →

browser_performance_audit

browser_performance_audit

Part of the Looking Glass MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

looking-glass-mcp Execute Risk 3/5

AI agents invoke browser_performance_audit to trigger processes or run actions in Looking Glass. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

browser_performance_audit can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-sahib-sawhney-wh-looking-glass-mcp.yaml
tools:
  browser_performance_audit:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Looking Glass policy for all 71 tools.

Tool Name browser_performance_audit
Category Execute
Risk Level High

View all 71 tools →

Agents calling execute-class tools like browser_performance_audit have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

browser_performance_audit is one of the high-risk operations in Looking Glass. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the browser_performance_audit tool do? +

browser_performance_audit. It is categorised as a Execute tool in the Looking Glass MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_performance_audit? +

Add a rule in your Intercept YAML policy under the tools section for browser_performance_audit. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Looking Glass MCP server.

What risk level is browser_performance_audit? +

browser_performance_audit is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browser_performance_audit? +

Yes. Add a rate_limit block to the browser_performance_audit rule in your Intercept 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 browser_performance_audit completely? +

Set action: deny in the Intercept policy for browser_performance_audit. 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 browser_performance_audit? +

browser_performance_audit is provided by the Looking Glass MCP server (looking-glass-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Looking Glass

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.