deck_get_card

Get full details of a Deck card including description, labels, and assigned users.

SERVERAIquila — Nextcloud MCP Server SOURCEelgorro/aiquila

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiquila-nextcloud-mcp-server/deck-get-card.md

WHAT IT DOES

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.

RISK

Why deck_get_card is rated Low

This tool queries and retrieves card information from Nextcloud Deck. It performs a read-only operation that returns existing data without creating, modifying, deleting, or executing any actions. The blast radius is minimal as the worst misuse would be unauthorized data access to card details, which is typical for read operations.

From the tool's definition Tool description states 'Get full details of a Deck card' — retrieves data with no mention of modification, deletion, or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

deck_get_card is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deck_get_card": {}
  }
}

ALLOW ONLY 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_get_card call is checked against it from then on.

FAQ

Questions about deck_get_card

What does the deck_get_card tool do? +

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.

How do I enforce a policy on deck_get_card? +

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.

What risk level is deck_get_card? +

deck_get_card is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit deck_get_card? +

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.

How do I block deck_get_card completely? +

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.

What MCP server provides deck_get_card? +

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.

KEEP EXPLORING

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

This server

All 295 AIquila — Nextcloud MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →