restartFrame · MCP Chrome Debugger Protocol MCP

WHAT IT DOES

What restartFrame does on MCP Chrome Debugger Protocol

AI agents invoke restartFrame 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 restartFrame needs a policy

Restarting a stack frame is an Execute-class action: it triggers an external operation (manipulation of a running process's execution state) whose effects depend on which frame is targeted. While not immediately destructive (data is not deleted), it is a dynamic code/execution manipulation with potential side effects and blast radius.

From the tool's definition Tool description states 'Restart execution from a specific stack frame' — this triggers control flow changes in a running Node.js process via the Chrome DevTools Protocol, altering the execution state of the debugged application.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restartFrame Rate-limited

restartFrame 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": {
    "restartFrame": {
      "limits": [
        {
          "counter": "restartframe_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 restartFrame

What does the restartFrame tool do? +

Restart execution from a specific stack frame (DAP standard). 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 restartFrame? +

Register the MCP Chrome Debugger Protocol MCP server in PolicyLayer and add a rule for restartFrame: 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 restartFrame? +

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

Can I rate-limit restartFrame? +

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

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

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