Low Risk

get_xrefs_from

Get all cross-references FROM a specific address (not just functions).

How to control get_xrefs_from ↓

What get_xrefs_from does on Kawaiidra MCP

AI agents call get_xrefs_from to retrieve information from Kawaiidra MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_xrefs_from needs a policy

This tool queries Ghidra's analysis database to retrieve cross-reference metadata. It performs no side effects, does not execute code, does not modify binaries or analysis state, and does not trigger external operations. It is purely informational, making it a Read operation with low severity.

From the tool's definition Tool description states 'Get all cross-references FROM a specific address' — a retrieval operation with no modification or execution capability. The verb 'Get' and the read-only nature of querying cross-reference data confirm this is a data retrieval function.

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

How to control get_xrefs_from

PolicyLayer is an MCP gateway — it sits between your AI agents and Kawaiidra MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_xrefs_from:

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

get_xrefs_from 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 Kawaiidra MCP — 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 get_xrefs_from

What does the get_xrefs_from tool do? +

Get all cross-references FROM a specific address (not just functions). It is categorised as a Read tool in the Kawaiidra MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_xrefs_from? +

Register the Kawaiidra MCP server in PolicyLayer and add a rule for get_xrefs_from: 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 Kawaiidra MCP. Nothing to install.

What risk level is get_xrefs_from? +

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

Can I rate-limit get_xrefs_from? +

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

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

get_xrefs_from is provided by the Kawaiidra MCP server (wagonbomb/kawaiidra-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kawaiidra MCP tool call.

Start from Kawaiidra MCP, 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.

94 Kawaiidra MCP 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.