xhr_breakpoint · JS Reverse MCP: Risk & Policy

WHAT IT DOES

What xhr_breakpoint does on JS Reverse MCP

AI agents invoke xhr_breakpoint to trigger actions in JS Reverse MCP. 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 xhr_breakpoint needs a policy

Setting an XHR/Fetch breakpoint is a browser debugging action that triggers execution pauses and intercepts network requests in the browser. This is an active browser manipulation operation that can affect running code behavior, fitting the Execute category. The blast radius is medium as it can intercept or disrupt network communications but doesn't directly delete data or move money.

From the tool's definition Set or remove an XHR/Fetch breakpoint by URL substring match

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

xhr_breakpoint Rate-limited

xhr_breakpoint 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": {
    "xhr_breakpoint": {
      "limits": [
        {
          "counter": "xhr_breakpoint_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 JS Reverse MCP, so you can run agents against it safely.

FAQ

Questions about xhr_breakpoint

What does the xhr_breakpoint tool do? +

Set or remove an XHR/Fetch breakpoint by URL substring match. It is categorised as a Execute tool in the JS Reverse MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on xhr_breakpoint? +

Register the JS Reverse MCP server in PolicyLayer and add a rule for xhr_breakpoint: 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 JS Reverse MCP. Nothing to install.

What risk level is xhr_breakpoint? +

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

Can I rate-limit xhr_breakpoint? +

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

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

xhr_breakpoint is provided by the JS Reverse MCP server (noone-hub/jsreverser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.