Sets a breakpoint on specific code (function name, statement, etc.) by searching for it and automatically determining the exact position. Works with both normal and minified files. NOTE: Prefer hook_function for monitoring function calls — it captures args/results without pausing execution. Use t...
AI agents invoke set_breakpoint_on_text to trigger actions in JS Reverse Strong 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 a breakpoint triggers an active debugging operation in the browser runtime — it modifies the execution environment by inserting a breakpoint that can pause execution. This is an Execute-category action as it triggers external browser operations and affects runtime behavior, going beyond simple data retrieval.
From the tool's definition Sets a breakpoint on specific code (function name, statement, etc.) by searching for it and automatically determining the exact position... Use this only when you need to inspect local variables at a specific code location.
Documented attack patterns abuse exactly the kind of access set_breakpoint_on_text gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JS Reverse Strong MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for set_breakpoint_on_text:
{
"version": "1",
"default": "deny",
"tools": {
"set_breakpoint_on_text": {
"limits": [
{
"counter": "set_breakpoint_on_text_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}set_breakpoint_on_text 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 on specific code (function name, statement, etc.) by searching for it and automatically determining the exact position. Works with both normal and minified files. NOTE: Prefer hook_function for monitoring function calls — it captures args/results without pausing execution. Use this only when you need to inspect local variables at a specific code location. It is categorised as a Execute tool in the JS Reverse Strong MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the JS Reverse Strong MCP server in PolicyLayer and add a rule for set_breakpoint_on_text: 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 Strong MCP. Nothing to install.
set_breakpoint_on_text 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 set_breakpoint_on_text 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 set_breakpoint_on_text. 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.
set_breakpoint_on_text is provided by the JS Reverse Strong MCP server (lwjjike/jsreverser-strong-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from JS Reverse Strong MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
85 JS Reverse Strong MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.