Low Risk

get_xrefs_to_field

Find all references to a field.

How to control get_xrefs_to_field ↓

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

Low Risk

This tool performs a search or analysis operation on decompiled Android code to locate where a specific field is referenced. It is purely informational and has no side effects—it does not execute code, modify data, delete anything, or move money. It fits the 'Read' category as it retrieves and queries existing analysis data from the JADX decompiler.

From the tool's definition Tool name 'get_xrefs_to_field' and description 'Find all references to a field' indicate a query/lookup operation that retrieves cross-reference information without modifying or executing any code.

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

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

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

get_xrefs_to_field 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 JADX-MCP-SERVER — 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.

Go deeper

What does the get_xrefs_to_field tool do? +

Find all references to a field. It is categorised as a Read tool in the JADX-MCP-SERVER MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_xrefs_to_field? +

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

What risk level is get_xrefs_to_field? +

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

Can I rate-limit get_xrefs_to_field? +

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

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

get_xrefs_to_field is provided by the JADX-MCP-SERVER MCP server (zinja-coder/jadx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every JADX-MCP-SERVER tool call.

Deterministic rules across all 32 JADX-MCP-SERVER tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

32 JADX-MCP-SERVER tools catalogued and risk-classified — across an index of 42,500+ 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.