deck_update_card

Update an existing Deck card. Provide only the fields you want to change. Fetches the current card first to preserve unchanged fields.

SERVERAIquila — Nextcloud MCP Server SOURCEelgorro/aiquila

Medium RISK CLASS

Category Write

Parameters 73 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-update-card.md

WHAT IT DOES

What deck_update_card does on AIquila — Nextcloud MCP Server

AI agents use deck_update_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
`done`	boolean	—	Mark card as done
`title`	string	—	New title
`cardId`	integer	Yes	Card ID (from deck_list_stacks)
`boardId`	integer	Yes	Board ID
`duedate`	object	—	Due date (ISO 8601) or null to clear
`stackId`	integer	Yes	Stack ID (from deck_list_stacks)
`description`	string	—	New description (Markdown)

Parameters from the server's own tool schema.

RISK

Why deck_update_card is rated Medium

The tool modifies existing card data in Nextcloud's Deck application. This is a Write operation because it creates or modifies data reversibly—updates can be undone by making subsequent updates. The severity is medium because misuse could modify task/project data affecting team workflows, but the operation is reversible and doesn't delete data or move money.

From the tool's definition Tool description states 'Update an existing Deck card' and 'Provide only the fields you want to change', indicating modification of existing data through a reversible operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

deck_update_card Rate-limited

deck_update_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_update_card": {
      "limits": [
        {
          "counter": "deck_update_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_update_card call is checked against it from then on.

FAQ

Questions about deck_update_card

What does the deck_update_card tool do? +

Update an existing Deck card. Provide only the fields you want to change. Fetches the current card first to preserve unchanged fields. 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_update_card accept? +

deck_update_card accepts 7 parameters: done, title, cardId, boardId, duedate, stackId, description. Required: cardId, boardId, stackId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on deck_update_card? +

Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for deck_update_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_update_card? +

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

Can I rate-limit deck_update_card? +

Yes. Add a rate_limit block to the deck_update_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_update_card completely? +

Set action: deny in the PolicyLayer policy for deck_update_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_update_card? +

deck_update_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

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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