Unified tool to read logs, capture crashes, check ANRs, and clear buffers.
AI agents invoke manage-logcat to trigger actions in Android Mcp Toolkit. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool combines read operations (read logs, capture crashes, check ANRs) with a potentially irreversible action (clear buffers). Per the rules, the most severe applicable category wins. Clearing logcat buffers is an external operation on the Android device that permanently discards buffered log data, placing it at Execute level (triggering external device operations).
From the tool's definition 'clear buffers' — clearing logcat buffers is a destructive/irreversible action; 'read logs, capture crashes, check ANRs' are read operations; 'Unified tool' spans multiple operations
Documented attack patterns abuse exactly the kind of access manage-logcat gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Android Mcp Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for manage-logcat:
{
"version": "1",
"default": "deny",
"tools": {
"manage-logcat": {
"limits": [
{
"counter": "manage-logcat_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}manage-logcat stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Unified tool to read logs, capture crashes, check ANRs, and clear buffers. It is categorised as a Execute tool in the Android Mcp Toolkit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Android Mcp Toolkit MCP server in PolicyLayer and add a rule for manage-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 Android Mcp Toolkit. Nothing to install.
manage-logcat is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the manage-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 manage-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.
manage-logcat is provided by the Android Mcp Toolkit MCP server (nam0101/android-mcp-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Android Mcp Toolkit, 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.
7 Android Mcp Toolkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.