AI agents call delete to permanently remove resources in VecFS — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data from storage without the ability to undo or recover the deleted entry. Deletion is an irreversible operation that causes data loss, placing it in the Destructive category.
From the tool's definition Tool name is 'delete' and description states 'Delete an entry from the vector space by its unique ID.' The verb 'delete' combined with 'by its unique ID' indicates irreversible removal of a specific memory entry.
Documented attack patterns abuse exactly the kind of access delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VecFS, and nothing reaches the server without passing your rules. This is the rule we recommend for delete:
{
"version": "1",
"default": "deny",
"hide": [
"delete"
]
}delete 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 an entry from the vector space by its unique ID. It is categorised as a Destructive tool in the VecFS MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the VecFS MCP server in PolicyLayer and add a rule for 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 VecFS. Nothing to install.
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 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 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.
delete is provided by the VecFS MCP server (wazzamo/vecfs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VecFS, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 VecFS tools catalogued and risk-classified — across an index of 43,000+ MCP servers.