Resume JavaScript execution after hitting a breakpoint.
AI agents invoke resume_execution to trigger actions in ReverseCraft DevTools MCP. 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.
This tool resumes paused JavaScript execution in a browser debugging context. It triggers continuation of code execution, which is an Execute-category action. Misuse could cause unintended code paths to run, but severity is medium since it only resumes already-paused execution rather than initiating new arbitrary code.
From the tool's definition Resume JavaScript execution after hitting a breakpoint
Documented attack patterns abuse exactly the kind of access resume_execution gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ReverseCraft DevTools MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for resume_execution:
{
"version": "1",
"default": "deny",
"tools": {
"resume_execution": {
"limits": [
{
"counter": "resume_execution_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} resume_execution 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.
Free to start. No card required.
Resume JavaScript execution after hitting a breakpoint. It is categorised as a Execute tool in the ReverseCraft DevTools MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ReverseCraft DevTools 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 ReverseCraft DevTools MCP. Nothing to install.
resume_execution is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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 ReverseCraft DevTools MCP server (reverse-craft/rc-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ReverseCraft DevTools MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
46 ReverseCraft DevTools MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.