search_in_source

THE RISK

Low Risk

Why search_in_source needs a policy

This tool retrieves information by searching source code text and regex patterns. It has no side effects—it does not create, modify, delete, execute, or move data. It is purely a read operation similar to grep or find functionality in code exploration. The low severity reflects minimal blast radius if misused by an agent: worst case is exposure of source code patterns already available locally.

From the tool's definition Tool performs searching and pattern matching within source code: 'Search for a text/regex pattern within a specific class or across all synced files'. The description indicates retrieval/query operations with no modification or execution of code.

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

POLICY

How to control search_in_source

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_in_source": {}
  }
}

search_in_source is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Android Source Explorer MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Android Source Explorer MCP Server tools

Read check_integrity Check the integrity of the local source cache and index. Read find_references Find all references to a symbol at a specific position (Requires LSP). Read get_class_hierarchy Get the inheritance hierarchy (superclass and interfaces) for a class. Read get_type_info Get type information and documentation (hover) for a symbol (Requires LSP). Read goto_definition Resolve the definition of a symbol at a specific position (Requires LSP). Read list_available_versions List available versions for an AndroidX artifact (e.g. 'androidx.compose.runtime:runtime') Read list_class_members List all method and field signatures for a given class. Read lookup_class Retrieve the full source code for a given Android Framework or AndroidX class.

All 11 Android Source Explorer MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about search_in_source

What does the search_in_source tool do? +

Search for a text/regex pattern within a specific class or across all synced files (if class_name is omitted). It is categorised as a Read tool in the Android Source Explorer MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_in_source? +

Register the Android Source Explorer MCP Server MCP server in PolicyLayer and add a rule for search_in_source: 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 Source Explorer MCP Server. Nothing to install.

What risk level is search_in_source? +

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

Can I rate-limit search_in_source? +

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

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

search_in_source is provided by the Android Source Explorer MCP Server MCP server (mrmike/android-source-explorer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Android Source Explorer MCP Server tool call.

Start from Android Source Explorer MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →