wavexis_cookies_delete

Delete cookies matching name and domain.

SERVERWavexis SOURCEMathiasPaulenko/wavexis-mcp
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/wavexis-mcp/wavexis-cookies-delete.md

What wavexis_cookies_delete does on Wavexis

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

Why wavexis_cookies_delete is rated Critical

Deleting cookies is an irreversible operation that permanently removes stored authentication tokens, session data, and user preferences. An AI agent misusing this tool could silently log users out of websites, destroy session state, or interfere with application functionality. While not as severe as deleting databases, cookie deletion cannot be undone programmatically and represents a destructive capability.

From the tool's definition Tool name and description: 'wavexis_cookies_delete' with description 'Delete cookies matching name and domain.' The verb 'Delete' combined with the irreversible nature of cookie removal indicates a destructive action.

Questions about wavexis_cookies_delete

What does the wavexis_cookies_delete tool do? +

Delete cookies matching name and domain. It is categorised as a Destructive tool in the Wavexis 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 wavexis_cookies_delete? +

Register the Wavexis MCP server in PolicyLayer and add a rule for wavexis_cookies_delete: 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 Wavexis. Nothing to install.

What risk level is wavexis_cookies_delete? +

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

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

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

wavexis_cookies_delete is provided by the Wavexis MCP server (MathiasPaulenko/wavexis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Wavexis, 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 Wavexis'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.