AI agents call list_instances 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 retrieves state information about IDA Pro instances. The verb 'list' is a read-only query operation with no side effects. The server context (reverse engineering, multi-instance support) confirms this lists available instances.
From the tool's definition Tool name is 'list_instances' which by convention retrieves or enumerates data. No description provided, but the name indicates a query operation that lists existing instances without modification.
Documented attack patterns abuse exactly the kind of access list_instances 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 list_instances:
{
"version": "1",
"default": "deny",
"tools": {
"list_instances": {}
}
}list_instances 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_instances. 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 list_instances: 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.
list_instances 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 list_instances 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 list_instances. 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.
list_instances 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.