Low Risk

get_strings

Retrieve contents of strings.xml files.

How to control get_strings ↓

AI agents call get_strings 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 queries the contents of Android resource files (strings.xml), which is a read-only operation that retrieves localized string constants used in Android applications. There is no capability to modify, execute, delete, or move financial resources. The context of a reverse engineering/decompilation server confirms this is purely for code inspection and analysis.

From the tool's definition Tool name 'get_strings' and description 'Retrieve contents of strings.xml files' indicate a query/fetch operation that retrieves static resource data without modification or side effects.

Documented attack patterns abuse exactly the kind of access get_strings 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_strings:

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

get_strings 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_strings tool do? +

Retrieve contents of strings.xml files. 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_strings? +

Register the JADX-MCP-SERVER MCP server in PolicyLayer and add a rule for get_strings: 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_strings? +

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

Can I rate-limit get_strings? +

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

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

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