planka_update_custom_field_value

WHAT IT DOES

What planka_update_custom_field_value does on Planka MCP Server for Claude

AI agents use planka_update_custom_field_value 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_update_custom_field_value needs a policy

Updating a custom field value modifies card data but does not delete, execute code, move money, or trigger external operations. It is reversible (the value can be changed again) and falls squarely in the Write category. Severity is medium because misuse could corrupt or pollute project management data, affecting team workflows, but the impact is limited to a single card's custom field and is easily correctable.

From the tool's definition Tool name 'planka_update_custom_field_value' and description 'Set a custom field value on a card' indicate modification of existing card metadata. This is a reversible write operation on a Planka kanban card's custom field.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

planka_update_custom_field_value Rate-limited

planka_update_custom_field_value 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_update_custom_field_value": {
      "limits": [
        {
          "counter": "planka_update_custom_field_value_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_update_custom_field_value

What does the planka_update_custom_field_value tool do? +

Set a custom field value on 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_update_custom_field_value? +

Register the Planka MCP Server for Claude MCP server in PolicyLayer and add a rule for planka_update_custom_field_value: 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_update_custom_field_value? +

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

Can I rate-limit planka_update_custom_field_value? +

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

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

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