AI agents call delete_sift to permanently remove resources in Sifter — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a sift (a structured document schema) and all associated records without any indication of reversibility or undo capability. Deleting 'all its records' represents a high blast radius if invoked unintentionally or maliciously by an AI agent, as it could result in loss of significant amounts of user data. This is a clear Destructive action per the classification rules.
From the tool's definition Tool name is 'delete_sift' and description states 'Delete a sift and all its records.' The use of 'delete' and 'all its records' explicitly indicates irreversible data removal.
Documented attack patterns abuse exactly the kind of access delete_sift gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sifter, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_sift:
{
"version": "1",
"default": "deny",
"hide": [
"delete_sift"
]
}delete_sift disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a sift and all its records. It is categorised as a Destructive tool in the Sifter MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sifter MCP server in PolicyLayer and add a rule for delete_sift: 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 Sifter. Nothing to install.
delete_sift 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_sift 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_sift. 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_sift is provided by the Sifter MCP server (sifter-ai/sifter). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Sifter tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Sifter tools catalogued and risk-classified — across an index of 42,500+ MCP servers.