Get information about the current default IDA instance
AI agents call get_current_instance to retrieve information from IDA Pro MCP Multi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only retrieval of metadata about the current IDA Pro instance. It does not modify data, execute code, delete resources, or commit financial obligations. The blast radius of misuse is minimal—an agent could only learn which instance is active, posing no direct risk to the system or data integrity.
From the tool's definition Tool name 'get_current_instance' and description 'Get information about the current default IDA instance' indicate a query operation that retrieves state information without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_current_instance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and IDA Pro MCP Multi, and nothing reaches the server without passing your rules. This is the rule we recommend for get_current_instance:
{
"version": "1",
"default": "deny",
"tools": {
"get_current_instance": {}
}
}get_current_instance 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.
Get information about the current default IDA instance. It is categorised as a Read tool in the IDA Pro MCP Multi MCP Server, which means it retrieves data without modifying state.
Register the IDA Pro MCP Multi MCP server in PolicyLayer and add a rule for get_current_instance: 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 Pro MCP Multi. Nothing to install.
get_current_instance 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_current_instance 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_current_instance. 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_current_instance is provided by the IDA Pro MCP Multi MCP server (qymag1c/ida-pro-mcp-multi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from IDA Pro MCP Multi, 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.
5 IDA Pro MCP Multi tools catalogued and risk-classified — across an index of 43,000+ MCP servers.