browser_sec_stop_csp_monitoring · Browser MCP: Risk & Policy

WHAT IT DOES

What browser_sec_stop_csp_monitoring does on Browser

AI agents invoke browser_sec_stop_csp_monitoring to trigger actions in Browser. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why browser_sec_stop_csp_monitoring needs a policy

This tool performs an action that triggers external effects on browser state (stopping a monitoring system and clearing data), which cannot be cleanly reversed and affects the security posture of the browser session. It is Execute rather than Write because it terminates an ongoing process and has side effects beyond simple data modification.

From the tool's definition Tool name contains 'stop_csp_monitoring' and description states 'Stop CSP monitoring and clear violations'. This modifies browser security state by terminating an active security monitoring mechanism and clearing accumulated security violation records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_sec_stop_csp_monitoring Rate-limited

browser_sec_stop_csp_monitoring stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_sec_stop_csp_monitoring": {
      "limits": [
        {
          "counter": "browser_sec_stop_csp_monitoring_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Browser, so you can run agents against it safely.

FAQ

Questions about browser_sec_stop_csp_monitoring

What does the browser_sec_stop_csp_monitoring tool do? +

Stop CSP monitoring and clear violations (see browser_docs). It is categorised as a Execute tool in the Browser 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_sec_stop_csp_monitoring? +

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

What risk level is browser_sec_stop_csp_monitoring? +

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

Can I rate-limit browser_sec_stop_csp_monitoring? +

Yes. Add a rate_limit block to the browser_sec_stop_csp_monitoring 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 browser_sec_stop_csp_monitoring completely? +

Set action: deny in the PolicyLayer policy for browser_sec_stop_csp_monitoring. 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_sec_stop_csp_monitoring? +

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