wavexis_cookies_delete

A destructive tool on the Pypi:wavexis MCP server.

SERVERPypi:wavexis 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 IT DOES

What wavexis_cookies_delete does on Pypi:wavexis

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

RISK

Why wavexis_cookies_delete is rated Critical

Deletes cookies irreversibly; could destroy authentication, sessions, or user preferences without recovery.

From the tool's definition uninformative description; tool name indicates irreversible deletion of cookies

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wavexis_cookies_delete safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pypi:wavexis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wavexis_cookies_delete, this is the rule to start with:

wavexis_cookies_delete Hidden

wavexis_cookies_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "wavexis_cookies_delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pypi:wavexis, apply this rule, and every wavexis_cookies_delete call is checked against it from then on.

FAQ

Questions about wavexis_cookies_delete

What does the wavexis_cookies_delete tool do? +

wavexis_cookies_delete is a destructive tool on the Pypi:wavexis MCP server. It is categorised as a Destructive tool in the Pypi: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 Pypi: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 Pypi: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 Pypi: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.

KEEP EXPLORING

More on Pypi:wavexis, and thousands of servers like it.

This server

All 220 Pypi:wavexis tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →