New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

system_clear_logs

Clear device log buffer (Android only)

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile
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/alexgladkov-claude-in-mobile/system-clear-logs.md

What system_clear_logs does on Claude Mobile

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

Why system_clear_logs is rated Critical

This tool permanently deletes system logs without reversibility. While the blast radius is narrower than data deletion affecting user content, logs are critical for security auditing, troubleshooting, and forensic analysis. An AI agent misusing this could cover tracks of malicious activity, hide errors, or destroy evidence.

From the tool's definition 'Clear device log buffer' irreversibly removes system logs from the device with no undo mechanism. The verb 'clear' combined with 'log buffer' indicates permanent deletion of data.

Risk signalsAdmin/system-level operation

Questions about system_clear_logs

What does the system_clear_logs tool do? +

Clear device log buffer (Android only). It is categorised as a Destructive tool in the Claude Mobile 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 system_clear_logs? +

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

What risk level is system_clear_logs? +

system_clear_logs 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 system_clear_logs? +

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

How do I block system_clear_logs completely? +

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

What MCP server provides system_clear_logs? +

system_clear_logs is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Claude Mobile, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Claude Mobile's. Pull the full record:

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.