Low Risk

xrefs_to

Get all cross-references to specified addresses

How to control xrefs_to ↓

What xrefs_to does on Ida Domain

AI agents call xrefs_to 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 xrefs_to needs a policy

This tool queries cross-reference information from an IDA Pro database, a read-only retrieval operation. It retrieves metadata about code references without executing code, modifying the database, or triggering external operations. The sibling tools (analyze_funcs, analyze_strings, basic_blocks, callers, callees, callgraph) are similarly informational.

From the tool's definition Tool name 'xrefs_to' and description 'Get all cross-references to specified addresses' indicate a query operation that retrieves data without modification or execution.

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

How to control xrefs_to

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

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

xrefs_to 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 xrefs_to

What does the xrefs_to tool do? +

Get all cross-references to specified addresses. 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 xrefs_to? +

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

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

Can I rate-limit xrefs_to? +

Yes. Add a rate_limit block to the xrefs_to 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 xrefs_to completely? +

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

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