info_locals

Get local variables.

Server WineDbg MCP Server maci0/mcp-winedbg
Category Read
Risk class Low
Parameters 00 required

What info_locals does on WineDbg MCP Server

AI agents call info_locals to retrieve information from WineDbg MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why info_locals needs a policy

This tool queries local variable values from a debugged process. It has no side effects, does not modify data, execute arbitrary code, delete resources, or affect financial systems. It is purely informational retrieval during debugging, consistent with Read category operations like 'get' or 'fetch'.

From the tool's definition Tool name 'info_locals' and description 'Get local variables' indicate a read-only operation that retrieves debugging information without modifying state or executing code.

Questions about info_locals

What does the info_locals tool do? +

Get local variables. It is categorised as a Read tool in the WineDbg MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on info_locals? +

Register the WineDbg MCP Server MCP server in PolicyLayer and add a rule for info_locals: 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 WineDbg MCP Server. Nothing to install.

What risk level is info_locals? +

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

Can I rate-limit info_locals? +

Yes. Add a rate_limit block to the info_locals 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 info_locals completely? +

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

info_locals is provided by the WineDbg MCP Server MCP server (maci0/mcp-winedbg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.