Get logcat output from the device
AI agents call adb_get_logcat to retrieve information from ADB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves diagnostic log data from an Android device without modifying, deleting, or executing anything. While logs may contain sensitive information, the operation itself is non-destructive and read-only. Severity is low because log retrieval has minimal blast radius — it gathers existing data without affecting system state or triggering external actions.
From the tool's definition Tool name 'adb_get_logcat' uses the verb 'get', and description states 'Get logcat output from the device' — logcat retrieves system and application logs, a read-only operation with no side effects.
Attacks that exploit this kind of access
Get logcat output from the device. It is categorised as a Read tool in the ADB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ADB MCP Server MCP server in PolicyLayer and add a rule for adb_get_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 ADB MCP Server. Nothing to install.
adb_get_logcat is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the adb_get_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.
Set action: deny in the PolicyLayer policy for adb_get_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.
adb_get_logcat is provided by the ADB MCP Server MCP server (richard0913/adb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →