Clear the Android logcat buffer.
AI agents call android_clear_logcat to permanently remove resources in DevLab MCP Suite — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing the logcat buffer irreversibly destroys all existing log data accumulated in the buffer. This cannot be undone — once cleared, historical log entries are permanently lost. While the blast radius is limited to diagnostic/log data (not user data or app state), the action is irreversible, placing it in the Destructive category.
From the tool's definition Clear the Android logcat buffer
Attacks that exploit this kind of access
Clear the Android logcat buffer. It is categorised as a Destructive tool in the DevLab MCP Suite MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DevLab MCP Suite MCP server in PolicyLayer and add a rule for android_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 DevLab MCP Suite. Nothing to install.
android_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 android_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 android_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.
android_clear_logcat is provided by the DevLab MCP Suite MCP server (tanguito86/devlab-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 →