Resumes JavaScript execution after being paused at a breakpoint. Execution continues until the next breakpoint or completion.
AI agents invoke resume to trigger actions in JS Reverse 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 triggers continuation of JavaScript execution in a browser debugging context. It causes code to run, which can have arbitrary side effects depending on what scripts are executing. This is an Execute-category action as it directly controls runtime execution flow in a browser environment.
From the tool's definition Resumes JavaScript execution after being paused at a breakpoint. Execution continues until the next breakpoint or completion.
Attacks that exploit this kind of access
Resumes JavaScript execution after being paused at a breakpoint. Execution continues until the next breakpoint or completion. It is categorised as a Execute tool in the JS Reverse MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the JS Reverse MCP server in PolicyLayer and add a rule for resume: 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 JS Reverse MCP. Nothing to install.
resume 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 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. 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 is provided by the JS Reverse MCP server (noone-hub/jsreverser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →