This record as markdown: /tools/io-github-fullread-deepadb/adb-logcat-clear.md
What adb_logcat_clear does on Deepadb
AI agents call adb_logcat_clear to permanently remove resources in Deepadb, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why adb_logcat_clear is rated Critical
Clearing logcat buffers irreversibly deletes diagnostic and operational logs from the Android device without the ability to recover them. While not directly damaging data or system state, this action destroys forensic evidence and operational history that cannot be restored. If an AI agent misused this tool without explicit user intent, it would eliminate crucial debugging information and audit trails.
From the tool's definition Tool name 'adb_logcat_clear' and description 'Clear all logcat buffers on the device' indicate irreversible deletion of device logs.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs adb_logcat_clear safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_logcat_clear, this is the rule to start with:
adb_logcat_clear is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_logcat_clear call is checked against it from then on.
Questions about adb_logcat_clear
Clear all logcat buffers on the device. It is categorised as a Destructive tool in the Deepadb MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_logcat_clear: 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 Deepadb. Nothing to install.
adb_logcat_clear 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 adb_logcat_clear 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 adb_logcat_clear. 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.
adb_logcat_clear is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadb, and thousands of servers like it.
Across the catalogue