Low Risk

get_xrefs_from

Get cross-references from an address

Part of the Ghidra MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@LaurieWired/GhidraMCP Read Risk 2/5

AI agents call get_xrefs_from to retrieve information from Ghidra without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_xrefs_from only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

ghidra.yaml
tools:
  get_xrefs_from:
    rules:
      - action: allow

See the full Ghidra policy for all 27 tools.

Tool Name get_xrefs_from
Category Read
MCP Server Ghidra MCP Server
Risk Level Low

View all 27 tools →

Agents calling read-class tools like get_xrefs_from have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the get_xrefs_from tool do? +

Get cross-references from an address. It is categorised as a Read tool in the Ghidra MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_xrefs_from? +

Add a rule in your Intercept YAML policy under the tools section for get_xrefs_from. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ghidra MCP server.

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 Intercept 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 Intercept 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 Ghidra MCP server (@LaurieWired/GhidraMCP). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Ghidra

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.