deck_assign_user

Assign a user to a Deck card.

SERVERAIquila — Nextcloud MCP Server SOURCEelgorro/aiquila

Medium RISK CLASS

Category Write

Parameters 44 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-assign-user.md

WHAT IT DOES

What deck_assign_user does on AIquila — Nextcloud MCP Server

AI agents use deck_assign_user 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
`cardId`	integer	Yes	Card ID
`userId`	string	Yes	User ID (login name) to assign
`boardId`	integer	Yes	Board ID
`stackId`	integer	Yes	Stack ID

Parameters from the server's own tool schema.

RISK

Why deck_assign_user is rated Medium

This tool modifies task/project management data (Deck cards) by assigning users, which is a Write operation. It creates or updates metadata on a card but does not delete data, execute arbitrary code, move money, or trigger external operations based on input.

From the tool's definition Tool name 'deck_assign_user' and description 'Assign a user to a Deck card' indicate modification of card metadata by adding a user assignment to a Deck card, which is a reversible change to data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

deck_assign_user Rate-limited

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

FAQ

Questions about deck_assign_user

What does the deck_assign_user tool do? +

Assign a user to a Deck card. 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_assign_user accept? +

deck_assign_user accepts 4 parameters: cardId, userId, boardId, stackId. Required: cardId, userId, 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_assign_user? +

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

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

Can I rate-limit deck_assign_user? +

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

Set action: deny in the PolicyLayer policy for deck_assign_user. 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_assign_user? +

deck_assign_user 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

The MCP Attack Database →

Guides

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