Get function arguments.
AI agents call info_args 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.
The tool queries runtime state of a debugged process (function arguments) which is a read operation. However, the severity is elevated to 'medium' rather than 'low' because in the context of a debugger with access to a running Windows application, retrieved argument data could contain sensitive information (credentials, tokens, PII) that an AI agent might exfiltrate or misuse, creating a moderate information…
From the tool's definition Tool name 'info_args' and description 'Get function arguments' indicate this retrieves debugging information about function parameters without modifying state.
Attacks that exploit this kind of access
Get function arguments. 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 info_args: 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.
info_args 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 info_args 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 info_args. 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.
info_args 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 →