Delete a flashcard by ID.
AI agents call delete_flashcard to permanently remove resources in Flashcard MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes flashcard data, which cannot be undone. While the blast radius is limited to individual learning records (not system-critical), the destructive nature and irreversibility of the operation place it in the Destructive category. Severity is medium rather than high because the impact is scoped to user flashcard data within a learning application, not production data or financial systems.
From the tool's definition Tool name is 'delete_flashcard' and description states 'Delete a flashcard by ID.' The verb 'Delete' combined with the action of removing a flashcard by identifier indicates irreversible data removal.
Attacks that exploit this kind of access
Delete a flashcard by ID. It is categorised as a Destructive tool in the Flashcard MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Flashcard MCP server in PolicyLayer and add a rule for delete_flashcard: 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 Flashcard MCP. Nothing to install.
delete_flashcard 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_flashcard 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_flashcard. 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_flashcard is provided by the Flashcard MCP server (louislva/flashcards-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 →