deck_create_stack
Create a new stack (column) on a Deck board.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/deck-create-stack.md
What deck_create_stack does on AIquila — Nextcloud MCP Server
AI agents use deck_create_stack 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 order (0-based) |
title | string | Yes | Stack title |
boardId | integer | Yes | Board ID (from deck_list_boards) |
Parameters from the server's own tool schema.
Why deck_create_stack is rated Medium
Creating a stack/column is a write operation that adds a new organizational container to a board. It is reversible (stacks can be deleted) and has minimal blast radius. The action modifies board structure but does not execute arbitrary code, delete data, or involve financial transactions. Low severity due to limited scope and reversibility.
From the tool's definition Tool name 'deck_create_stack' with description 'Create a new stack (column) on a Deck board' indicates creation of a new data structure within Nextcloud Deck.
Attacks that exploit this kind of access
The rule that runs deck_create_stack 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_stack, this is the rule to start with:
deck_create_stack 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_stack call is checked against it from then on.
Questions about deck_create_stack
Create a new stack (column) on a Deck board. 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_stack accepts 3 parameters: order, title, boardId. Required: title, boardId. 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_stack: 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_stack 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_stack 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_stack. 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_stack 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