Delete a prompt from your library (requires explicit confirmation)
AI agents call delete_prompt to permanently remove resources in Prompteka MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes prompts from the user's local library stored in SQLite. Deletion is irreversible and cannot be undone through the tool itself. While the confirmation requirement adds a safety measure, it does not prevent an AI agent from intentionally confirming deletion.
From the tool's definition Tool name 'delete_prompt' and description 'Delete a prompt from your library' indicate irreversible deletion of data.
Attacks that exploit this kind of access
Delete a prompt from your library (requires explicit confirmation). It is categorised as a Destructive tool in the Prompteka MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Prompteka MCP Server 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 Prompteka MCP Server. 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 Prompteka MCP Server MCP server (webdevguyrg/prompteka-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 →