Close the project's IDA database and terminate its worker process.
AI agents call close_database to permanently remove resources in Ida Domain — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Closing the IDA database and terminating the worker process is irreversible in the context of the session — any unsaved analysis, changes, or state will be lost. Terminating a process is also not easily undone. This constitutes a destructive action with a high blast radius if triggered unintentionally during active reverse engineering workflows.
From the tool's definition 'Close the project's IDA database and terminate its worker process'
Documented attack patterns abuse exactly the kind of access close_database 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 close_database:
{
"version": "1",
"default": "deny",
"hide": [
"close_database"
]
}close_database disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Close the project's IDA database and terminate its worker process. It is categorised as a Destructive tool in the Ida Domain MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ida Domain MCP server in PolicyLayer and add a rule for close_database: 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.
close_database is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the close_database 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 close_database. 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.
close_database 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.