breakpoint
Manage breakpoints: code (line/script), function-name, XHR (URL pattern), event listener, event category, and exception breakpoints.\n\nActions:\n- set: Create a breakpoint. Type determines required params.\n- remove: Remove a breakpoint by ID.\n- list: List active breakpoints of the given type.\...
This record as markdown: /tools/io-github-vmoranv-jshookmcp/breakpoint.md
What breakpoint does on Jshookmcp
AI agents invoke breakpoint to trigger actions in Jshookmcp. 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 breakpoint is rated High
Sets/removes breakpoints that control JavaScript execution flow in a browser/runtime environment.
From the tool's definition Manage breakpoints: code, function-name, XHR, event listener, exception
Attacks that exploit this kind of access
The rule that runs breakpoint safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For breakpoint, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every breakpoint call is checked against it from then on.
Questions about breakpoint
Manage breakpoints: code (line/script), function-name, XHR (URL pattern), event listener, event category, and exception breakpoints.\n\nActions:\n- set: Create a breakpoint. Type determines required params.\n- remove: Remove a breakpoint by ID.\n- list: List active breakpoints of the given type.\n\nTypes & params:\n- code: lineNumber (required), scriptId?, columnNumber?, condition?, logMessage? (logpoint: logs without pausing)\n- function: functionName (required for set) — resolves via globalThis lookup and breaks whenever that function is called\n- xhr: urlPattern (required for set)\n- event: eventName (required for set), targetName?\n- event_category: category (required for set)\n- exception: state (required for set). It is categorised as a Execute tool in the Jshookmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Jshook MCP server in PolicyLayer and add a rule for 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 Jshookmcp. Nothing to install.
breakpoint 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 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.
Set action: deny in the PolicyLayer policy for 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.
breakpoint is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Jshook, and thousands of servers like it.
Across the catalogue