Wipe all browser logs from memory
AI agents call wipeLogs to permanently remove resources in BrowserTools MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes browser console and network logs from memory, which cannot be undone. While the data loss is scoped to in-memory logs rather than persistent storage, it still constitutes irreversible destruction of debugging information that may be needed for incident investigation, security analysis, or troubleshooting.
From the tool's definition Tool name 'wipeLogs' and description 'Wipe all browser logs from memory' indicate irreversible deletion of data. The verb 'wipe' combined with 'all browser logs' demonstrates permanent removal without recovery option.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Wipe all browser logs from memory. It is categorised as a Destructive tool in the BrowserTools MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the BrowserTools MCP server in PolicyLayer and add a rule for wipeLogs: 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 BrowserTools MCP. Nothing to install.
wipeLogs 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 wipeLogs 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 wipeLogs. 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.
wipeLogs is provided by the BrowserTools MCP server (sugatraj/cursor-browser-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →