AI agents call adb_logcat to retrieve information from LocalAnt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing Android system logs without creating, modifying, deleting, or executing any actions. It has no side effects on the system state. While logs may contain sensitive information, the classification is based on the action performed (retrieval), not the sensitivity of the data. The blast radius is minimal—an agent cannot cause damage by reading logs.
From the tool's definition Tool name 'adb_logcat' and description 'Dump recent logcat output' indicate retrieval of system logs without modification. The verb 'dump' in this context means to output/retrieve, not to delete or clear (contrast with sibling tool 'adb_clear_logcat').
Attacks that exploit this kind of access
Dump recent logcat output. It is categorised as a Read tool in the LocalAnt MCP Server, which means it retrieves data without modifying state.
Register the LocalAnt MCP server in PolicyLayer and add a rule for adb_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 LocalAnt. Nothing to install.
adb_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_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_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_logcat is provided by the LocalAnt MCP server (yuga-hashimoto/localant). 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 →