deck_create_card
Create a new card in a Deck stack.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/deck-create-card.md
What deck_create_card does on AIquila — Nextcloud MCP Server
AI agents use deck_create_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 |
|---|---|---|---|
title | string | Yes | Card title |
boardId | integer | Yes | Board ID |
duedate | string | — | Due date in ISO 8601 format (e.g. 2025-12-31) |
stackId | integer | Yes | Stack ID (from deck_list_stacks) |
description | string | — | Card description (Markdown) |
Parameters from the server's own tool schema.
Why deck_create_card is rated Medium
This tool creates a new card (reversible data creation) in a Deck stack without deleting, executing code, or moving money. The impact is limited to task/project management metadata within Nextcloud. Severity is medium because uncontrolled card creation could spam or clutter a user's task board, but the action is reversible via deletion and affects only the Deck application scope.
From the tool's definition Tool name 'deck_create_card' and description 'Create a new card in a Deck stack' indicate creation of new data within Nextcloud's Deck (task management) application.
Attacks that exploit this kind of access
The rule that runs deck_create_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_create_card, this is the rule to start with:
deck_create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every deck_create_card call is checked against it from then on.
Questions about deck_create_card
Create a new card in a Deck stack. 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_create_card accepts 5 parameters: title, boardId, duedate, stackId, description. Required: title, boardId, 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_create_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.
deck_create_card 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_create_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.
Set action: deny in the PolicyLayer policy for deck_create_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.
deck_create_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.
This server
Across the catalogue