AI agents use duplicate_card to create or update resources in Framedeck — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Framedeck environment.
This tool creates a new card (reversible write operation) by duplicating an existing one. It does not execute code, delete data irreversibly, move money, or have destructive effects. The operation is typical of content management systems and can be undone by deleting the duplicate. The blast radius is minimal—worst case, duplicate cards clutter a board but cause no data loss or external side effects.
From the tool's definition Tool name 'duplicate_card' and description 'Duplicate a card including its checklist items' indicate creation of new content by copying existing data.
Attacks that exploit this kind of access
Duplicate a card including its checklist items. It is categorised as a Write tool in the Framedeck MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Framedeck MCP server in PolicyLayer and add a rule for duplicate_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.
duplicate_card is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the duplicate_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 duplicate_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.
duplicate_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 →