New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

deck_assign_label

Assign a label to a Deck card. Use deck_get_board to see available labels and their IDs.

Medium RISK CLASS
Category Write
Parameters 44 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about deck_assign_label

What does the deck_assign_label tool do? +

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.

What parameters does deck_assign_label accept? +

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.

How do I enforce a policy on deck_assign_label? +

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.

What risk level is deck_assign_label? +

deck_assign_label is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit deck_assign_label? +

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.

How do I block deck_assign_label completely? +

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.

What MCP server provides deck_assign_label? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of AIquila — Nextcloud MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.