deletes cookies from the current browser session. Can delete a specific cookie by name or all cookies.
AI agents call delete_cookie to permanently remove resources in Mcp Selenium — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool irreversibly removes cookies from the browser session. Deleting cookies cannot be undone within the session and may cause loss of authentication state, session data, or user preferences. Deleting all cookies is a broad destructive action, warranting the Destructive category.
From the tool's definition 'deletes cookies from the current browser session. Can delete a specific cookie by name or all cookies.'
Attacks that exploit this kind of access
deletes cookies from the current browser session. Can delete a specific cookie by name or all cookies. It is categorised as a Destructive tool in the Mcp Selenium MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Selenium MCP server in PolicyLayer and add a rule for delete_cookie: 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 Mcp Selenium. Nothing to install.
delete_cookie 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 delete_cookie 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 delete_cookie. 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.
delete_cookie is provided by the Mcp Selenium MCP server (@angiejones/mcp-selenium). 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 →