planka_unassign_user_from_card

WHAT IT DOES

What planka_unassign_user_from_card does on Planka MCP Server for Claude

AI agents use planka_unassign_user_from_card to create or update resources in Planka MCP Server for Claude — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Planka MCP Server for Claude environment.

WHY IT NEEDS A POLICY

Why planka_unassign_user_from_card needs a policy

Unassigning a user from a card modifies the card's state by removing a user assignment, which is a Write-category operation (creates/modifies data reversibly). Severity is medium because misuse could disrupt project workflow by incorrectly removing task assignments, but the action is fully reversible by reassigning the user.

From the tool's definition Tool name 'planka_unassign_user_from_card' and description 'Unassign a user from a card' indicate modification of card assignment state. This is a reversible write operation that changes card metadata without deleting data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

planka_unassign_user_from_card Rate-limited

planka_unassign_user_from_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "planka_unassign_user_from_card": {
      "limits": [
        {
          "counter": "planka_unassign_user_from_card_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Planka MCP Server for Claude, so you can run agents against it safely.

FAQ

Questions about planka_unassign_user_from_card

What does the planka_unassign_user_from_card tool do? +

Unassign a user from a card. It is categorised as a Write tool in the Planka MCP Server for Claude MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on planka_unassign_user_from_card? +

Register the Planka MCP Server for Claude MCP server in PolicyLayer and add a rule for planka_unassign_user_from_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 Planka MCP Server for Claude. Nothing to install.

What risk level is planka_unassign_user_from_card? +

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

Can I rate-limit planka_unassign_user_from_card? +

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

Set action: deny in the PolicyLayer policy for planka_unassign_user_from_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 planka_unassign_user_from_card? +

planka_unassign_user_from_card is provided by the Planka MCP Server for Claude MCP server (nextheberg/planka-mcp-server-for-claude). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.