adb_clear_logcat

Clear the logcat buffer.

SERVERLocalAnt SOURCEyuga-hashimoto/localant

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yuga-hashimoto-localant/adb-clear-logcat.md

WHAT IT DOES

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.

RISK

Why adb_clear_logcat is rated Critical

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_clear_logcat safely

PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_clear_logcat, this is the rule to start with:

adb_clear_logcat Hidden

adb_clear_logcat is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "adb_clear_logcat"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect LocalAnt, apply this rule, and every adb_clear_logcat call is checked against it from then on.

FAQ

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.

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools → Critical-risk tools on this server →

Across the catalogue

clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP →clear_spam_box on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →