get_variables

THE RISK

Low Risk

Why get_variables needs a policy

This tool retrieves variable information from a paused debugger context. While it is read-only with no side effects on the target program, the severity is elevated to medium because debugger access can expose sensitive data (API keys, tokens, passwords, PII) that may be present in variables during program execution.

From the tool's definition Tool name 'get_variables' and description 'Get variables for the latest paused call frame scope' indicate data retrieval with no modification or execution. The tool queries the state of variables in a debugger session.

Documented attack patterns abuse exactly the kind of access get_variables gives an agent:

POLICY

How to control get_variables

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Debugger Node, and nothing reaches the server without passing your rules. This is the rule we recommend for get_variables:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_variables": {}
  }
}

get_variables is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Mcp Debugger Node — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Mcp Debugger Node tools

Execute reset Restart the debug session with a fresh Node inspector process for the provided target. Execute stop Stop the current debug target and clear the debug session. Execute wait_for_pause Wait until the debugged Node.js process pauses and return the current location. Execute continue Resume execution of the debugged Node.js process and return immediately. Execute evaluate Evaluate a JavaScript expression in the debugged runtime. Execute resume Resume execution of the debugged Node.js process and wait for the next pause. Execute set_breakpoint Set a breakpoint by matching a script URL with a regex. Execute set_pause_on_exceptions Configure whether the debugger pauses on no exceptions, uncaught exceptions, or all except

All 11 Mcp Debugger Node tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_variables

What does the get_variables tool do? +

Get variables for the latest paused call frame scope. It is categorised as a Read tool in the Mcp Debugger Node MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_variables? +

Register the Mcp Debugger Node MCP server in PolicyLayer and add a rule for get_variables: 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 Mcp Debugger Node. Nothing to install.

What risk level is get_variables? +

get_variables is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_variables? +

Yes. Add a rate_limit block to the get_variables 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.

How do I block get_variables completely? +

Set action: deny in the PolicyLayer policy for get_variables. 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.

What MCP server provides get_variables? +

get_variables is provided by the Mcp Debugger Node MCP server (mohammed-almassri/mcp-debugger-node). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Debugger Node tool call.

Start from Mcp Debugger Node, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →