logcat

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

SERVERFrida Agent MCP SOURCE1193776794/frida-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

WHAT IT DOES

What logcat does on Frida Agent MCP

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

RISK

Why logcat is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs logcat safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Frida Agent MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For logcat, this is the rule to start with:

logcat Allowed

logcat is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Frida Agent MCP, apply this rule, and every logcat call is checked against it from then on.

FAQ

Questions about logcat

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.

KEEP EXPLORING

More on Frida Agent, and thousands of servers like it.

This server

All 10 Frida Agent tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →