adb_clear_logcat

Clear the logcat buffer.

Server LocalAnt yuga-hashimoto/localant
Category Destructive
Risk class Critical
Parameters 00 required

What adb_clear_logcat does on LocalAnt

AI agents call adb_clear_logcat to permanently remove resources in LocalAnt — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why adb_clear_logcat needs a policy

Clearing the logcat buffer permanently removes all existing log entries from the Android device's log buffer. This action cannot be undone, making it Destructive. While the blast radius is moderate (log data loss, potential loss of forensic/diagnostic evidence), it does not affect user data or system functionality directly.

From the tool's definition 'Clear the logcat buffer' — clearing the buffer irreversibly destroys existing log data

Questions about adb_clear_logcat

What does the adb_clear_logcat tool do? +

Clear the logcat buffer. It is categorised as a Destructive tool in the LocalAnt MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on adb_clear_logcat? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for adb_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 LocalAnt. Nothing to install.

What risk level is adb_clear_logcat? +

adb_clear_logcat is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit adb_clear_logcat? +

Yes. Add a rate_limit block to the adb_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.

How do I block adb_clear_logcat completely? +

Set action: deny in the PolicyLayer policy for adb_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.

What MCP server provides adb_clear_logcat? +

adb_clear_logcat is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.