AI agents call clear-logcat to permanently remove resources in ADB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently erases device log data without the ability to undo or recover the information. While log deletion itself is not catastrophic compared to app/system data loss, it represents an irreversible destructive action on device state. The logs could be important for debugging or forensics. Classified as Destructive rather than Write because the action cannot be reversed.
From the tool's definition clear-logcat 清除设备上的日志缓冲区 (clears the device's log buffer) - this irreversibly deletes log data that cannot be recovered once cleared.
Documented attack patterns abuse exactly the kind of access clear-logcat gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ADB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for clear-logcat:
{
"version": "1",
"default": "deny",
"hide": [
"clear-logcat"
]
}clear-logcat disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
清除设备上的日志缓冲区. It is categorised as a Destructive tool in the ADB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ADB MCP Server MCP server in PolicyLayer and add a rule for clear-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.
clear-logcat is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear-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 clear-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.
clear-logcat is provided by the ADB MCP Server MCP server (jiantao88/android-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ADB MCP Server, 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.
30 ADB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.