List imported functions for a module: importing DLL name, function name, ordinal, IAT address.
AI agents call get_imports to retrieve information from x64dbg MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a static analysis operation that queries and retrieves information about a module's import table. It has no side effects, does not execute code, does not modify binaries or memory, and does not trigger external operations. It is purely informational, fitting the 'Read' category.
From the tool's definition Tool name 'get_imports' and description explicitly states it 'List[s] imported functions for a module' with no modification or deletion capability—only retrieval of metadata (DLL names, function names, ordinals, IAT addresses).
Attacks that exploit this kind of access
List imported functions for a module: importing DLL name, function name, ordinal, IAT address. It is categorised as a Read tool in the x64dbg MCP Server MCP Server, which means it retrieves data without modifying state.
Register the x64dbg MCP Server MCP server in PolicyLayer and add a rule for get_imports: 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 x64dbg MCP Server. Nothing to install.
get_imports 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_imports 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_imports. 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_imports is provided by the x64dbg MCP Server MCP server (ouonet/x64dbg-mcp). 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 →