Deletes a prompt from the project-specific directory. If a user global default with the same ID exists, it will become active.
AI agents call delete_prompt to permanently remove resources in Prompt Registry MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (a prompt template) that cannot be recovered unless backed up externally. While the blast radius is contained to prompt templates rather than production data, deletion is inherently destructive. The fallback to global defaults does not undo the deletion itself.
From the tool's definition Tool name is 'delete_prompt' and description states it 'Deletes a prompt from the project-specific directory.' The verb 'deletes' combined with removal from storage indicates an irreversible deletion operation.
Documented attack patterns abuse exactly the kind of access delete_prompt gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Prompt Registry MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_prompt:
{
"version": "1",
"default": "deny",
"hide": [
"delete_prompt"
]
} delete_prompt 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.
Deletes a prompt from the project-specific directory. If a user global default with the same ID exists, it will become active. It is categorised as a Destructive tool in the Prompt Registry MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Prompt Registry MCP server in PolicyLayer and add a rule for delete_prompt: 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 Prompt Registry MCP. Nothing to install.
delete_prompt 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_prompt 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_prompt. 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_prompt is provided by the Prompt Registry MCP server (stevengonsalvez/promptregistry-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Prompt Registry MCP, 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.
7 Prompt Registry MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.