AI agents call delete_project to permanently remove resources in Forgetful — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool's name unambiguously indicates deletion of a project entity from the persistent knowledge base. Deletion is irreversible and cannot be undone. While the description is empty, the naming convention and context of sibling destructive tools on the Forgetful server confirm this operates in the Destructive category.
From the tool's definition Tool name is 'delete_project' with no description provided. Sibling tools include 'delete_code_artifact', 'delete_document', 'delete_entity', establishing a clear pattern of destructive operations on this server.
Documented attack patterns abuse exactly the kind of access delete_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Forgetful, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_project:
{
"version": "1",
"default": "deny",
"hide": [
"delete_project"
]
}delete_project 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_project. It is categorised as a Destructive tool in the Forgetful MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Forgetful MCP server in PolicyLayer and add a rule for delete_project: 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 Forgetful. Nothing to install.
delete_project 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_project 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_project. 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_project is provided by the Forgetful MCP server (scottrbk/forgetful). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 59 Forgetful tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
59 Forgetful tools catalogued and risk-classified — across an index of 42,500+ MCP servers.