Delete a corpus's settings row. Cascade=True also deletes its
AI agents call files_corpus_delete to permanently remove resources in M3 Memory — 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 the memory corpus. Even though it appears to primarily delete metadata (settings row), the cascade=True flag indicates it can trigger deletion of associated data records. Deletion is irreversible and cannot be undone, making this Destructive rather than Write.
From the tool's definition Tool name is 'files_corpus_delete' and description states 'Delete a corpus's settings row. Cascade=True also deletes its' (text cut off, but indicates cascading deletion). The word 'Delete' combined with cascade behavior indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access files_corpus_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and M3 Memory, and nothing reaches the server without passing your rules. This is the rule we recommend for files_corpus_delete:
{
"version": "1",
"default": "deny",
"hide": [
"files_corpus_delete"
]
}files_corpus_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 a corpus's settings row. Cascade=True also deletes its. It is categorised as a Destructive tool in the M3 Memory MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the M3 Memory MCP server in PolicyLayer and add a rule for files_corpus_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 M3 Memory. Nothing to install.
files_corpus_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 files_corpus_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 files_corpus_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.
files_corpus_delete is provided by the M3 Memory MCP server (skynetcmd/m3-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from M3 Memory, 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.
43 M3 Memory tools catalogued and risk-classified — across an index of 43,000+ MCP servers.