清除设备日志缓冲区
AI agents call clear_logcat to permanently remove resources in Android ADB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call clear_logcat doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Android ADB MCP Server is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
清除设备日志缓冲区. It is categorised as a Destructive tool in the Android ADB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Android 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 Android 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 Android ADB MCP Server MCP server (xuegao-tzx/android-adb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.