Permanently delete a card/frame
AI agents call delete_card to permanently remove resources in Framedeck — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data (a card/frame) from the Framedeck production management system. Permanent deletion cannot be undone, meeting the definition of Destructive category. Severity is high because deleting a card could lose production content, checklist progress, comments, and associated metadata for YouTube/Instagram/TikTok/Podcast productions.
From the tool's definition Tool name is 'delete_card' and description states 'Permanently delete a card/frame'. The word 'Permanently' indicates irreversible deletion with no undo capability.
Attacks that exploit this kind of access
Permanently delete a card/frame. It is categorised as a Destructive tool in the Framedeck MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Framedeck MCP server in PolicyLayer and add a rule for delete_card: 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 Framedeck. Nothing to install.
delete_card 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_card 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_card. 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_card is provided by the Framedeck MCP server (lukaris/framedeck-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 →