Low Risk

find_api_calls

Search decompiled sources for API calls and endpoints.

How to control find_api_calls ↓

What find_api_calls does on Android Reverse Engineering

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

Low Risk

Why find_api_calls needs a policy

This tool performs static analysis by searching through decompiled source code for API patterns. It retrieves and queries information from previously decompiled APK files without modifying them or executing any code. The operation is read-only with no side effects, making it a Read category tool with low severity risk.

From the tool's definition Tool name 'find_api_calls' and description 'Search decompiled sources for API calls and endpoints' indicates a search/query operation over already-decompiled Android APK data.

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

How to control find_api_calls

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

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

find_api_calls 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 Android Reverse Engineering — 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 find_api_calls

What does the find_api_calls tool do? +

Search decompiled sources for API calls and endpoints. It is categorised as a Read tool in the Android Reverse Engineering MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_api_calls? +

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

What risk level is find_api_calls? +

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

Can I rate-limit find_api_calls? +

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

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

find_api_calls is provided by the Android Reverse Engineering MCP server (vichhka-git/android-reverse-engineering-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 Android Reverse Engineering tool call.

Start from Android Reverse Engineering, 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.

6 Android Reverse Engineering 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.