Inspect variables in the current scope (locals, globals, etc.) during debugging. See all variable values instantly - no more hovering over each one
AI agents call debug_inspectVariables to retrieve information from MCP Server for VS Code without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays variable values during a debugging session. It has no side effects—it does not modify variables, execute code, delete data, or trigger external operations. The action is purely informational, analogous to a Read operation. Even in a debugging context, inspecting variables is a passive query operation.
From the tool's definition Tool name 'debug_inspectVariables' and description 'Inspect variables in the current scope (locals, globals, etc.) during debugging. See all variable values instantly' indicate read-only retrieval of variable state without modification or execution.
Documented attack patterns abuse exactly the kind of access debug_inspectVariables gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for VS Code, and nothing reaches the server without passing your rules. This is the rule we recommend for debug_inspectVariables:
{
"version": "1",
"default": "deny",
"tools": {
"debug_inspectVariables": {}
}
}debug_inspectVariables 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 variables in the current scope (locals, globals, etc.) during debugging. See all variable values instantly - no more hovering over each one. It is categorised as a Read tool in the MCP Server for VS Code MCP Server, which means it retrieves data without modifying state.
Register the MCP Server for VS Code MCP server in PolicyLayer and add a rule for debug_inspectVariables: 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 Server for VS Code. Nothing to install.
debug_inspectVariables 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_inspectVariables 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_inspectVariables. 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_inspectVariables is provided by the MCP Server for VS Code MCP server (malvex/mcp-server-vscode). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server for VS Code, 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.
25 MCP Server for VS Code tools catalogued and risk-classified — across an index of 43,000+ MCP servers.