Sets a breakpoint that triggers when an XHR/Fetch request URL contains the specified string.
AI agents invoke break_on_xhr to trigger actions in MiniApp CDP 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.
Setting an XHR breakpoint is an active operation that modifies the runtime debugging state of a running process. It intercepts and pauses execution when matching network requests are made, which constitutes triggering external operations/affecting execution flow rather than merely reading data.
From the tool's definition 'Sets a breakpoint that triggers when an XHR/Fetch request URL contains the specified string' — this actively configures debugging state in the Chrome DevTools Protocol runtime, affecting program execution flow
Documented attack patterns abuse exactly the kind of access break_on_xhr gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MiniApp CDP MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for break_on_xhr:
{
"version": "1",
"default": "deny",
"tools": {
"break_on_xhr": {
"limits": [
{
"counter": "break_on_xhr_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} break_on_xhr 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.
Free to start. No card required.
Sets a breakpoint that triggers when an XHR/Fetch request URL contains the specified string. It is categorised as a Execute tool in the MiniApp CDP MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MiniApp CDP MCP server in PolicyLayer and add a rule for break_on_xhr: 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 MiniApp CDP MCP. Nothing to install.
break_on_xhr is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the break_on_xhr 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 break_on_xhr. 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.
break_on_xhr is provided by the MiniApp CDP MCP server (zhizhuodemao/miniapp-cdp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 MiniApp CDP MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 MiniApp CDP MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.