resume

Part of the Chrome Debugger MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents use resume to create or modify resources in Chrome Debugger MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON RESUME

Without a policy, an AI agent could call resume repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Chrome Debugger MCP.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

chrome-debugger-mcp.yaml

tools:
  resume:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Chrome Debugger MCP policy for all 18 tools.

// DETAILS

Tool Name resume

Category Write

MCP Server Chrome Debugger MCP MCP Server

Risk Level Medium

// MORE CHROME DEBUGGER MCP TOOLS

Destructive forcePause Destructive removeBreakpoint Execute evaluate Execute launchChrome Execute reloadPage Execute startDebuggingSession Execute stepInto Execute stepOut

View all 18 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like resume have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the resume tool do? +

[STEP 8] Resume script execution after collecting all needed variable data — ends the current pause. After calling resume, remove all temporary debugger; statements added to source code during this session. Relay the "_ui" field from the response to the user.. It is categorised as a Write tool in the Chrome Debugger 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 resume? +

Add a rule in your Intercept YAML policy under the tools section for resume. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Chrome Debugger MCP MCP server.

What risk level is resume? +

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

Can I rate-limit resume? +

Yes. Add a rate_limit block to the resume rule in your Intercept 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 resume completely? +

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

resume is provided by the Chrome Debugger MCP MCP server (chrome-debugger-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

resume

Enforce policies on Chrome Debugger MCP