continue · MCP Chrome Debugger Protocol MCP: Risk & Policy

WHAT IT DOES

What continue does on MCP Chrome Debugger Protocol

AI agents invoke continue to trigger actions in MCP Chrome Debugger Protocol. 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 IT NEEDS A POLICY

Why continue needs a policy

This tool resumes execution of a paused Node.js process via the Debug Adapter Protocol. It triggers external execution flow in a running process, which qualifies as Execute. Misuse could cause a debugged process to proceed past breakpoints unexpectedly, potentially bypassing security checks or causing unintended behavior in the target application.

From the tool's definition Continue execution (DAP standard name for resume)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

continue Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "continue": {
      "limits": [
        {
          "counter": "continue_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 Chrome Debugger Protocol, so you can run agents against it safely.

FAQ

Questions about continue

What does the continue tool do? +

Continue execution (DAP standard name for resume). It is categorised as a Execute tool in the MCP Chrome Debugger Protocol MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on continue? +

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

What risk level is continue? +

continue is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit continue? +

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

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

continue is provided by the MCP Chrome Debugger Protocol MCP server (vitalyostanin/mcp-chrome-debugger-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.