Archive a card. Use this for cards that are done and no longer needed in active view.
AI agents use codecks_archive_card to create or update resources in Codecks MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Codecks MCP Server environment.
Archiving modifies card state reversibly rather than permanently destroying data (which would be Destructive). While it changes visibility/status, it is a Write operation as it alters card metadata without triggering external code execution.
From the tool's definition Tool name and description: 'Archive a card' — archives/removes cards from active view. Archiving is a reversible state change (cards can be unarchived), not permanent deletion.
Attacks that exploit this kind of access
Archive a card. Use this for cards that are done and no longer needed in active view. It is categorised as a Write tool in the Codecks MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Codecks MCP Server MCP server in PolicyLayer and add a rule for codecks_archive_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 Codecks MCP Server. Nothing to install.
codecks_archive_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 codecks_archive_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 codecks_archive_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.
codecks_archive_card is provided by the Codecks MCP Server MCP server (microkorg/codecks-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 →