AI agents invoke continue_to_location to trigger actions in Node Js Debugger 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.
Based on the server context (Node.js debugger with stepping capabilities) and sibling tools, 'continue_to_location' almost certainly resumes execution of a debugged program until it reaches a specified source location — a debugger stepping/control operation. This falls under Execute as it triggers external program execution.
From the tool's definition Tool name 'continue_to_location' in context of a Node.js Debugger MCP server with Chrome DevTools Protocol capabilities including breakpoints and stepping
Documented attack patterns abuse exactly the kind of access continue_to_location gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Node Js Debugger MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for continue_to_location:
{
"version": "1",
"default": "deny",
"tools": {
"continue_to_location": {
"limits": [
{
"counter": "continue_to_location_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}continue_to_location 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.
continue_to_location. It is categorised as a Execute tool in the Node Js Debugger MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Node Js Debugger MCP server in PolicyLayer and add a rule for continue_to_location: 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 Node Js Debugger MCP. Nothing to install.
continue_to_location 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 continue_to_location 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 continue_to_location. 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.
continue_to_location is provided by the Node Js Debugger MCP server (scriptedalchemy/devtools-debugger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Node Js Debugger MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Node Js Debugger MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.