Low Risk

check_integrity

Check the integrity of the local source cache and index.

How to control check_integrity ↓

What check_integrity does on Android Source Explorer MCP Server

AI agents call check_integrity to retrieve information from Android Source Explorer MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why check_integrity needs a policy

This tool reads and validates the state of cached source code and indexes without creating, modifying, deleting, or executing anything. It is a diagnostic read operation with negligible security risk if misused—an AI agent invoking it cannot corrupt data, trigger code execution, or cause side effects. Severity is low because the tool surface is purely introspective.

From the tool's definition Tool name and description indicate 'Check the integrity of the local source cache and index' — a validation/inspection operation with no modification or execution of external commands.

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

How to control check_integrity

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 check_integrity:

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

check_integrity 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 Source Explorer 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.

Related tools and policies

Go deeper

Questions about check_integrity

What does the check_integrity tool do? +

Check the integrity of the local source cache and index. 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 check_integrity? +

Register the Android Source Explorer MCP Server MCP server in PolicyLayer and add a rule for check_integrity: 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 check_integrity? +

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

Can I rate-limit check_integrity? +

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

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

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

Free to start. No card required.

11 Android Source Explorer MCP Server 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.