deck_assign_label
Assign a label to a Deck card. Use deck_get_board to see available labels and their IDs.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/deck-assign-label.md
What deck_assign_label does on AIquila — Nextcloud MCP Server
AI agents use deck_assign_label 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 |
boardId | integer | Yes | Board ID |
labelId | integer | Yes | Label ID (from deck_get_board) |
stackId | integer | Yes | Stack ID |
Parameters from the server's own tool schema.
Why deck_assign_label is rated Medium
The tool assigns a label to a card, which creates or modifies data (the label association) reversibly. This is a classic Write operation. The severity is low because label assignment is a non-critical metadata change with minimal blast radius—it does not affect data integrity, delete information, execute code, or create financial obligations.
From the tool's definition "Assign a label to a Deck card" — this modifies metadata on an existing card by adding a label, which is a reversible write operation.
Attacks that exploit this kind of access
The rule that runs deck_assign_label 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_assign_label, this is the rule to start with:
deck_assign_label 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_assign_label call is checked against it from then on.
Questions about deck_assign_label
Assign a label to a Deck card. Use deck_get_board to see available labels and their IDs. 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_assign_label accepts 4 parameters: cardId, boardId, labelId, stackId. Required: cardId, boardId, labelId, 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_assign_label: 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_assign_label 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_assign_label 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_assign_label. 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_assign_label 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