Clear all captured network requests for a session.
AI agents call browser_clear_requests to permanently remove resources in Playwright MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes/clears captured network request data for a session. While the blast radius is low (only affects captured request logs, not external systems or persistent data), the action cannot be undone once the captured requests are cleared, making it Destructive rather than Write.
From the tool's definition Clear all captured network requests for a session
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all captured network requests for a session. It is categorised as a Destructive tool in the Playwright MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Playwright MCP Server MCP server in PolicyLayer and add a rule for browser_clear_requests: 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 Playwright MCP Server. Nothing to install.
browser_clear_requests 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 browser_clear_requests 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 browser_clear_requests. 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.
browser_clear_requests is provided by the Playwright MCP Server MCP server (leviathangk/playwrightmcpforcrawler). 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 →