Get the WINEDEBUG environment variable.
AI agents call get_debug_channels 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.
This tool performs a read-only query of an environment variable to retrieve debug channel configuration. It has no side effects, does not execute code, and does not modify any data. While it provides information about the Wine debugging environment, the information itself is not sensitive operational data that would cause significant harm if exposed to an AI agent.
From the tool's definition Tool queries the `WINEDEBUG` environment variable, returning its current value without modifying any state. The description explicitly states 'Get the `WINEDEBUG` environment variable', which is a retrieval operation.
Attacks that exploit this kind of access
Get the WINEDEBUG environment variable. It is categorised as a Read tool in the WineDbg MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WineDbg MCP Server MCP server in PolicyLayer and add a rule for get_debug_channels: 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.
get_debug_channels 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_debug_channels 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_debug_channels. 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_debug_channels 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.
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 →