deck_move_card

Move a card to a different stack (column) on the same board. This is the core kanban action for changing card status.

Medium RISK CLASS
Category Write
Parameters 00 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-move-card.md

What deck_move_card does on AIquila — Nextcloud MCP Server

AI agents use deck_move_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.

Why deck_move_card is rated Medium

The tool modifies existing data (card position/status) reversibly within a kanban board, which is a Write operation. The severity is medium because misuse could disrupt project workflow and organization, but the effect is easily reversible (a card can be moved back). It does not delete data, execute arbitrary code, or trigger financial transactions.

From the tool's definition Tool description states 'Move a card to a different stack (column) on the same board' — a modify operation that changes the state of a project card.

Questions about deck_move_card

What does the deck_move_card tool do? +

Move a card to a different stack (column) on the same board. This is the core kanban action for changing card status. 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.

How do I enforce a policy on deck_move_card? +

Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for deck_move_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.

What risk level is deck_move_card? +

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

Can I rate-limit deck_move_card? +

Yes. Add a rate_limit block to the deck_move_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.

How do I block deck_move_card completely? +

Set action: deny in the PolicyLayer policy for deck_move_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.

What MCP server provides deck_move_card? +

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

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