Low Risk

local_types

List local types

How to control local_types ↓

What local_types does on Ida Domain

AI agents call local_types 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.

Low Risk

Why local_types needs a policy

This tool queries and returns information about local types defined in a reverse engineering database. It has no side effects, does not execute code, does not modify data, and does not delete anything. It is purely informational in nature, consistent with other analysis tools like 'analyze_strings' and 'analyze_funcs' that inspect program metadata.

From the tool's definition Tool name 'local_types' with description 'List local types' indicates data retrieval from an IDA Pro database without modification or execution. The verb 'list' is a classic read operation that retrieves information about existing types.

Documented attack patterns abuse exactly the kind of access local_types gives an agent:

How to control local_types

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 local_types:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "local_types": {}
  }
}

local_types is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Ida Domain — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about local_types

What does the local_types tool do? +

List local types. It is categorised as a Read tool in the Ida Domain MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on local_types? +

Register the Ida Domain MCP server in PolicyLayer and add a rule for local_types: 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.

What risk level is local_types? +

local_types is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit local_types? +

Yes. Add a rate_limit block to the local_types 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.

How do I block local_types completely? +

Set action: deny in the PolicyLayer policy for local_types. 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.

What MCP server provides local_types? +

local_types 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.

Enforce policy on every Ida Domain tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.