Resume execution when debugger is paused
AI agents use resume_execution to create or update resources in Chrome DevTools MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Chrome DevTools MCP Server environment.
An AI agent can call resume_execution faster than any human can review — one bad instruction and it creates or modifies resources in Chrome DevTools MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Resume execution when debugger is paused. It is categorised as a Write tool in the Chrome DevTools MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Chrome DevTools MCP Server MCP server in PolicyLayer and add a rule for resume_execution: 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 Chrome DevTools MCP Server. Nothing to install.
resume_execution is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the resume_execution 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.
Set action: deny in the PolicyLayer policy for resume_execution. 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.
resume_execution is provided by the Chrome DevTools MCP Server MCP server (xrealsys/chrome-devtool-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.