wipe_logs

Clear all stored logs from memory

Server Chromium ARM64 Browser nfodor/mcp-chromium-arm64
Category Destructive
Risk class Critical
Parameters 00 required

What wipe_logs does on Chromium ARM64 Browser

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

Why wipe_logs needs a policy

The tool irreversibly clears/wipes all stored logs from memory. Once cleared, the log data cannot be recovered, making this a destructive operation. Severity is medium because it affects diagnostic/audit data (console logs, network logs) rather than primary application data, but loss of logs could impair debugging and security auditing.

From the tool's definition Clear all stored logs from memory

Risk signalsBulk/mass operation — affects multiple targets

Questions about wipe_logs

What does the wipe_logs tool do? +

Clear all stored logs from memory. It is categorised as a Destructive tool in the Chromium ARM64 Browser 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 wipe_logs? +

Register the Chromium ARM64 Browser MCP server in PolicyLayer and add a rule for wipe_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 Chromium ARM64 Browser. Nothing to install.

What risk level is wipe_logs? +

wipe_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 wipe_logs? +

Yes. Add a rate_limit block to the wipe_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 wipe_logs completely? +

Set action: deny in the PolicyLayer policy for wipe_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 wipe_logs? +

wipe_logs is provided by the Chromium ARM64 Browser MCP server (nfodor/mcp-chromium-arm64). 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.