Low Risk

logcat

Get Android logcat output. Useful for debugging crashes after script injection.

How to control logcat ↓

AI agents call logcat to retrieve information from Frida Agent MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Logcat is a read-only operation that captures system logs from an Android device. It does not modify, delete, or execute any code—it only retrieves and displays existing log data. While the server context involves dynamic analysis and code injection (which are Execute/Destructive operations), this specific tool is purely informational.

From the tool's definition Tool retrieves Android logcat output for debugging purposes. The description explicitly states it is for 'debugging crashes after script injection' and uses the verb 'Get', indicating data retrieval with no side effects.

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

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

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

logcat 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 Frida Agent MCP — 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 logcat tool do? +

Get Android logcat output. Useful for debugging crashes after script injection. It is categorised as a Read tool in the Frida Agent MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on logcat? +

Register the Frida Agent MCP server in PolicyLayer and add a rule for logcat: 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 Frida Agent MCP. Nothing to install.

What risk level is logcat? +

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

Can I rate-limit logcat? +

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

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

logcat is provided by the Frida Agent MCP server (1193776794/frida-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Frida Agent MCP tool call.

Deterministic rules across all 10 Frida Agent MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

10 Frida Agent MCP 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.