Inspect all variable values at the current execution point. This is your window into program state - see what data looks like at runtime, verify assumptions, identify unexpected values, and understand why code behaves as it does.
AI agents call get_variables_values to retrieve information from DebugMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and inspects runtime state without modifying code, data, or execution flow. It is purely a read operation that queries the debugger for variable information. While it operates within a debugging context (which involves some control), the tool itself performs no side effects, executes no code, and modifies nothing.
From the tool's definition Tool name 'get_variables_values' and description stating 'Inspect all variable values at the current execution point' with language emphasizing observation ('see what data looks like', 'verify assumptions', 'identify unexpected values') rather than…
Documented attack patterns abuse exactly the kind of access get_variables_values gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DebugMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_variables_values:
{
"version": "1",
"default": "deny",
"tools": {
"get_variables_values": {}
}
}get_variables_values 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.
Inspect all variable values at the current execution point. This is your window into program state - see what data looks like at runtime, verify assumptions, identify unexpected values, and understand why code behaves as it does. It is categorised as a Read tool in the DebugMCP MCP Server, which means it retrieves data without modifying state.
Register the Debug MCP server in PolicyLayer and add a rule for get_variables_values: 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 DebugMCP. Nothing to install.
get_variables_values 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_variables_values 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_variables_values. 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_variables_values is provided by the Debug MCP server (microsoft/debugmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DebugMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 DebugMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.