AI agents call get_pause_info to retrieve information from Node Js Debugger MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite empty description, the tool name and server context strongly indicate this retrieves debugging state without modifying the debugged application. Confidence is slightly reduced due to missing explicit description, but the pattern of sibling tools and 'get_' prefix provide sufficient evidence for Read classification.
From the tool's definition Tool name 'get_pause_info' and context as a Node.js debugger indicates it retrieves debugging state information (pause location, breakpoint status, stack trace context).
Documented attack patterns abuse exactly the kind of access get_pause_info 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 get_pause_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_pause_info": {}
}
}get_pause_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_pause_info. It is categorised as a Read tool in the Node Js Debugger MCP MCP Server, which means it retrieves data without modifying state.
Register the Node Js Debugger MCP server in PolicyLayer and add a rule for get_pause_info: 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.
get_pause_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_pause_info 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 get_pause_info. 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.
get_pause_info 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.