Get shared library info.
AI agents call info_share 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 retrieves metadata about shared libraries loaded in the Wine-debugged process. It is a passive information-gathering operation with no side effects. While debugger access itself is sensitive, this specific tool only reads and reports library information, making it a Read category operation with low severity since it cannot modify system state or execute arbitrary code on its own.
From the tool's definition Tool name 'info_share' and description 'Get shared library info' indicate a read-only query operation that retrieves information about shared libraries in a debugged process. No modifications, deletions, or code execution are performed.
Attacks that exploit this kind of access
Get shared library info. 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_share: 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_share 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_share 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_share. 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_share 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 →