deck_get_card
Get full details of a Deck card including description, labels, and assigned users.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/deck-get-card.md
What deck_get_card does on AIquila — Nextcloud MCP Server
AI agents call deck_get_card to retrieve information from AIquila — Nextcloud MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
cardId | integer | Yes | Card ID (from deck_list_stacks) |
boardId | integer | Yes | Board ID |
stackId | integer | Yes | Stack ID (from deck_list_stacks) |
Parameters from the server's own tool schema.
Why deck_get_card is rated Low
This tool queries and returns information about a card in Nextcloud Deck. It performs no data modification, deletion, or external execution. The operation is read-only with minimal blast radius if misused by an agent—it would only expose already-existing data within the Nextcloud instance that the authenticated user can access.
From the tool's definition Tool name and description indicate retrieval operation: 'Get full details of a Deck card'. The verb 'get' and the phrase 'including description, labels, and assigned users' confirm this is a query operation that retrieves existing data without modification or…
Attacks that exploit this kind of access
The rule that runs deck_get_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_get_card, this is the rule to start with:
deck_get_card is read-only, so it stays allowed. 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_get_card call is checked against it from then on.
Questions about deck_get_card
Get full details of a Deck card including description, labels, and assigned users. It is categorised as a Read tool in the AIquila — Nextcloud MCP Server MCP Server, which means it retrieves data without modifying state.
deck_get_card accepts 3 parameters: cardId, boardId, stackId. Required: cardId, 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_get_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_get_card is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the deck_get_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_get_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_get_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