Get local variables for the current stack frame. This is a convenience tool that returns just the local variables without needing to traverse stack->scopes->variables manually
AI agents call get_local_variables to retrieve information from Mcp Debugger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only debugging introspection tool that retrieves state information during a debug session. It has no side effects, cannot modify data, execute code, or trigger external operations. The blast radius of misuse is minimal—an attacker gains visibility into variable values in memory, which is sensitive but non-destructive. Classified as Read with low severity.
From the tool's definition Tool name is 'get_local_variables' and description states it 'returns just the local variables' from the current stack frame. The verb 'get' and 'returns' indicate retrieval only, with no modification or execution of code.
Attacks that exploit this kind of access
Get local variables for the current stack frame. This is a convenience tool that returns just the local variables without needing to traverse stack->scopes->variables manually. It is categorised as a Read tool in the Mcp Debugger MCP Server, which means it retrieves data without modifying state.
Register the Mcp Debugger MCP server in PolicyLayer and add a rule for get_local_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. Nothing to install.
get_local_variables 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_local_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.
Set action: deny in the PolicyLayer policy for get_local_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.
get_local_variables is provided by the Mcp Debugger MCP server (@debugmcp/mcp-debugger). 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 →