disable_debugger

THE RISK

Medium Risk

Why disable_debugger needs a policy

This tool modifies the debugging state of the current page by disabling the JavaScript debugger and removing all breakpoints. While it removes breakpoints (which could be considered destructive), breakpoints can be re-added, making this a reversible modification. The primary action is changing debugger configuration state, which fits the Write category.

From the tool's definition Disable the JavaScript debugger on the current page and remove all breakpoints

Documented attack patterns abuse exactly the kind of access disable_debugger gives an agent:

POLICY

How to control disable_debugger

PolicyLayer is an MCP gateway — it sits between your AI agents and ReverseCraft DevTools MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for disable_debugger:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "disable_debugger": {
      "limits": [
        {
          "counter": "disable_debugger_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

disable_debugger stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register ReverseCraft DevTools MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More ReverseCraft DevTools MCP tools

Destructive clear_cookies Clear browser cookies for all sites or a specific domain. Destructive clear_persistent_scripts Remove all registered persistent scripts for the current page at once. This is useful for Destructive clear_script_replacements Remove all script replacement rules for the current page. Destructive remove_persistent_script Remove a previously registered persistent script by its identifier. After removal, the sc Destructive remove_script_replacement Remove a script replacement rule by its ID. Destructive remove_xhr_breakpoint Remove a previously set XHR/Fetch breakpoint by its URL pattern, or remove all XHR breakpo Destructive close_page Closes the page by its index. The last open page cannot be closed. Execute navigate_page Navigates the currently selected page to a URL.

All 46 ReverseCraft DevTools MCP tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about disable_debugger

What does the disable_debugger tool do? +

Disable the JavaScript debugger on the current page and remove all breakpoints. It is categorised as a Write tool in the ReverseCraft DevTools MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on disable_debugger? +

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

What risk level is disable_debugger? +

disable_debugger is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit disable_debugger? +

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

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

disable_debugger is provided by the ReverseCraft DevTools MCP server (reverse-craft/rc-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ReverseCraft DevTools MCP tool call.

Start from ReverseCraft DevTools MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →