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.

SERVERAIquila — Nextcloud MCP Server SOURCEelgorro/aiquila

Medium RISK CLASS

Category Write

Parameters 54 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 IT DOES

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.

Parameter	Type	Required	Description
`order`	integer	—	Position in target stack (0 = top). Defaults to 0
`cardId`	integer	Yes	Card ID
`boardId`	integer	Yes	Board ID
`stackId`	integer	Yes	Current stack ID of the card
`targetStackId`	integer	Yes	Destination stack ID

Parameters from the server's own tool schema.

RISK

Why deck_move_card is rated Medium

This tool modifies the state of a project management board by changing a card's position/status. It is reversible (the card can be moved back), causes no data loss, and does not execute arbitrary code or trigger external operations. It fits the Write category (creates or modifies data reversibly).

From the tool's definition Tool name 'deck_move_card' and description 'Move a card to a different stack (column) on the same board' indicate modification of kanban board state by relocating a card.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs deck_move_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_move_card, this is the rule to start with:

deck_move_card Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deck_move_card": {
      "limits": [
        {
          "counter": "deck_move_card_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every deck_move_card call is checked against it from then on.

FAQ

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.

What parameters does deck_move_card accept? +

deck_move_card accepts 5 parameters: order, cardId, boardId, stackId, targetStackId. Required: cardId, boardId, stackId, targetStackId. The full parameter table on this page comes from the server's own tool schema.

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.

KEEP EXPLORING

More on AIquila — Nextcloud MCP Server, and thousands of servers like it.

This server

All 301 AIquila — Nextcloud MCP Server tools →

Across the catalogue

move-task on Kanban MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →