delete_prompt
AI agents call delete_prompt to permanently remove resources in Prompt Store MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the description is empty, the function name 'delete_prompt' clearly indicates this tool permanently removes prompt records from the local SQLite database. This is a destructive operation that cannot be undone and results in data loss. Within the context of a personal prompt library (where data has user value), this is classified as Destructive rather than Write.
From the tool's definition Tool name 'delete_prompt' combined with server context of persistent SQLite storage for a personal prompt library. The tool name explicitly indicates irreversible deletion of stored data.
Attacks that exploit this kind of access
delete_prompt. It is categorised as a Destructive tool in the Prompt Store MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Prompt Store 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 Store 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 Store MCP server (mhoshdev/prompt-store-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →