deck_archive_card
Archive or unarchive a Deck card.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/deck-archive-card.md
What deck_archive_card does on AIquila — Nextcloud MCP Server
AI agents use deck_archive_card to create or update resources in AIquila — Nextcloud MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AIquila — Nextcloud MCP Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
cardId | integer | Yes | Card ID |
archive | boolean | — | true to archive, false to unarchive |
boardId | integer | Yes | Board ID |
stackId | integer | Yes | Stack ID |
Parameters from the server's own tool schema.
Why deck_archive_card is rated Medium
Archiving is a reversible state change operation that modifies data without permanently deleting it. The card can be unarchived to restore it to its previous state, making this a Write operation rather than Destructive. While it changes card visibility/status, the impact is limited to a single card and reversible, warranting medium severity rather than high.
From the tool's definition Tool name 'deck_archive_card' and description 'Archive or unarchive a Deck card' indicate the tool modifies the state of a card by archiving or unarchiving it.
Attacks that exploit this kind of access
The rule that runs deck_archive_card safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AIquila — Nextcloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deck_archive_card, this is the rule to start with:
deck_archive_card stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every deck_archive_card call is checked against it from then on.
Questions about deck_archive_card
Archive or unarchive a Deck card. It is categorised as a Write tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
deck_archive_card accepts 4 parameters: cardId, archive, boardId, stackId. Required: cardId, boardId, stackId. The full parameter table on this page comes from the server's own tool schema.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for deck_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 AIquila — Nextcloud MCP Server. Nothing to install.
deck_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 deck_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 deck_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.
deck_archive_card is provided by the AIquila — Nextcloud MCP Server MCP server (elgorro/aiquila). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AIquila — Nextcloud MCP Server, and thousands of servers like it.
This server
Across the catalogue