AI agents call imports to retrieve information from Ida Domain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves import information from a reverse engineering database (IDA Pro), performing a query operation that does not modify, execute, or delete data. It has 'medium' severity because importing information from a reverse-engineered binary could inform reconnaissance or vulnerability research, but the tool itself is a passive read operation with limited blast radius for misuse.
From the tool's definition Tool name 'imports' and description 'List imports' indicate data retrieval with no modification. Imports are read-only metadata about external function/library dependencies.
Documented attack patterns abuse exactly the kind of access imports gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ida Domain, and nothing reaches the server without passing your rules. This is the rule we recommend for imports:
{
"version": "1",
"default": "deny",
"tools": {
"imports": {}
}
}imports is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List imports. It is categorised as a Read tool in the Ida Domain MCP Server, which means it retrieves data without modifying state.
Register the Ida Domain MCP server in PolicyLayer and add a rule for 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 Ida Domain. Nothing to install.
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 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 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.
imports is provided by the Ida Domain MCP server (xxyyue/ida_domain_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ida Domain, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
74 Ida Domain tools catalogued and risk-classified — across an index of 43,000+ MCP servers.