Searches for all methods matching the provided name. Returns class and method pairs as string.
AI agents call search_method_by_name 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.
This is a straightforward search/query operation on decompiled code metadata. It has no capability to modify code, execute operations, or delete data. The blast radius is minimal; misuse would only expose information about method names in the analyzed codebase, which is already available through reading the decompiled source directly.
From the tool's definition Tool searches for methods matching a name and returns class and method pairs as strings. It performs a query operation with no side effects—it retrieves information about code structure without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access search_method_by_name 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 search_method_by_name:
{
"version": "1",
"default": "deny",
"tools": {
"search_method_by_name": {}
}
}search_method_by_name is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Searches for all methods matching the provided name. Returns class and method pairs as string. It is categorised as a Read tool in the Jadx MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jadx MCP Server MCP server in PolicyLayer and add a rule for search_method_by_name: 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.
search_method_by_name is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_method_by_name 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.
Set action: deny in the PolicyLayer policy for search_method_by_name. 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.
search_method_by_name is provided by the Jadx MCP Server MCP server (mobilehackinglab/jadx-mcp-plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jadx MCP Server, 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.
13 Jadx MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.