Remove stored CellarTracker credentials and cached wine data from this machine.
AI agents call clear-user-data to permanently remove resources in CellarTracker MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call clear-user-data doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from CellarTracker MCP is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Remove stored CellarTracker credentials and cached wine data from this machine. It is categorised as a Destructive tool in the CellarTracker MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CellarTracker MCP server in PolicyLayer and add a rule for clear-user-data: 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 CellarTracker MCP. Nothing to install.
clear-user-data 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 clear-user-data 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 clear-user-data. 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.
clear-user-data is provided by the CellarTracker MCP server (slavins-co/cellartracker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.