Get variables from a scope or compound variable.
AI agents call debug_get_variables to retrieve information from Polybugger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches variable values from a debugger scope, which is a read-only query operation. It retrieves data for inspection purposes without creating, modifying, deleting, or executing code. While it may provide sensitive information about program state (potentially increasing situational awareness for an attacker), the tool itself has no side effects and cannot be weaponized directly.
From the tool's definition Tool name and description: 'Get variables from a scope or compound variable' — retrieves/queries debug state information with no modification capability.
Attacks that exploit this kind of access
Get variables from a scope or compound variable. It is categorised as a Read tool in the Polybugger MCP Server, which means it retrieves data without modifying state.
Register the Polybugger MCP server in PolicyLayer and add a rule for debug_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 Polybugger. Nothing to install.
debug_get_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 debug_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.
Set action: deny in the PolicyLayer policy for debug_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.
debug_get_variables is provided by the Polybugger MCP server (wilfoa/polybugger-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 →