Soft-delete a record — it becomes invisible to store_get and store_search but is retained
AI agents call store_delete to permanently remove resources in Willow — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although described as 'soft-delete' (retained physically), the operation irreversibly removes data accessibility and visibility in normal queries. This prevents recovery through standard store_get and store_search operations. In a multi-application system with SAP/1.0 authorization, an AI agent misusing this tool could delete critical records across applications, causing data loss from an operational standpoint.
From the tool's definition Tool name 'store_delete' and description states it 'Soft-delete a record' — removal of data is irreversible from the application perspective, even if physically retained in the database.
Attacks that exploit this kind of access
Soft-delete a record — it becomes invisible to store_get and store_search but is retained. It is categorised as a Destructive tool in the Willow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Willow MCP server in PolicyLayer and add a rule for store_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 Willow. Nothing to install.
store_delete 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 store_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.
Set action: deny in the PolicyLayer policy for store_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.
store_delete is provided by the Willow MCP server (rudi193-cmd/willow-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 →