planka_update_task · Another Planka MCP: Risk & Policy

WHAT IT DOES

What planka_update_task does on Another Planka MCP

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

WHY IT NEEDS A POLICY

Why planka_update_task needs a policy

The tool updates task state within a Planka board system. While the description is empty, context from the server purpose ('create, and update projects, boards, and cards') and sibling tools confirms this performs reversible data modification. Severity is medium because task updates affect project data but lack the irreversibility of deletion or financial impact.

From the tool's definition Tool name 'planka_update_task' indicates modification of existing task data. Sibling tools include 'mcp_add_task' (Write) and 'mcp_delete_task' (Destructive), establishing this server's pattern of task management operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

planka_update_task Rate-limited

planka_update_task 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_task": {
      "limits": [
        {
          "counter": "planka_update_task_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 Another Planka MCP, so you can run agents against it safely.

FAQ

Questions about planka_update_task

What does the planka_update_task tool do? +

planka_update_task. It is categorised as a Write tool in the Another Planka MCP 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_task? +

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

What risk level is planka_update_task? +

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

Can I rate-limit planka_update_task? +

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

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

planka_update_task is provided by the Another Planka MCP server (roelven/another-planka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.