Remove an item from the shopping list, unconditionally and irreversibly (no soft-delete, not affected by list
AI agents call delete_shopping_item to permanently remove resources in Pantrist — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion operation on user data (shopping list items) with no undo capability or recovery mechanism. This meets the definition of Destructive category. While the blast radius is limited to shopping list data (not critical systems), the irreversibility and unconditional nature warrant high severity.
From the tool's definition Tool description explicitly states: 'Remove an item from the shopping list, unconditionally and irreversibly (no soft-delete...'
Attacks that exploit this kind of access
Remove an item from the shopping list, unconditionally and irreversibly (no soft-delete, not affected by list. It is categorised as a Destructive tool in the Pantrist MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pantrist MCP server in PolicyLayer and add a rule for delete_shopping_item: 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 Pantrist. Nothing to install.
delete_shopping_item 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_shopping_item 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_shopping_item. 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_shopping_item is provided by the Pantrist MCP server (pantrist-dev/pantrist-mcp). 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 →