disconnect_debugger · MCP JS Debugger MCP: Risk & Policy

WHAT IT DOES

What disconnect_debugger does on MCP JS Debugger

AI agents use disconnect_debugger to create or update resources in MCP JS Debugger — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP JS Debugger environment.

WHY IT NEEDS A POLICY

Why disconnect_debugger needs a policy

An AI agent can call disconnect_debugger faster than any human can review — one bad instruction and it creates or modifies resources in MCP JS Debugger by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disconnect_debugger Rate-limited

disconnect_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.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP JS Debugger, so you can run agents against it safely.

FAQ

Questions about disconnect_debugger

What does the disconnect_debugger tool do? +

Closes an active debugging session and releases all resources. It is categorised as a Write tool in the MCP JS Debugger MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on disconnect_debugger? +

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

What risk level is disconnect_debugger? +

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

Can I rate-limit disconnect_debugger? +

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

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

disconnect_debugger is provided by the MCP JS Debugger MCP server (johngrimes/mcp-js-debugger). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.