Clear logs from logcat on a specific Android device
AI agents call clear_device_logs to permanently remove resources in Android Device — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes device logs without restoration capability, which is a destructive action. While not directly threatening user data or financial assets, it removes evidence/audit trails and could impede forensic analysis or debugging. The destructive nature elevates it above Write (which is reversible) despite the contained scope to log files rather than application data.
From the tool's definition Tool name 'clear_device_logs' combined with description 'Clear logs from logcat on a specific Android device' indicates irreversible deletion of log data.
Attacks that exploit this kind of access
Clear logs from logcat on a specific Android device. It is categorised as a Destructive tool in the Android Device MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Android Device MCP server in PolicyLayer and add a rule for clear_device_logs: 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 Device. Nothing to install.
clear_device_logs 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_device_logs 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_device_logs. 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_device_logs is provided by the Android Device MCP server (prashant1507/android-device-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 →