planka_update_notification

WHAT IT DOES

What planka_update_notification does on Planka MCP Server for Claude

AI agents use planka_update_notification 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_notification needs a policy

The tool updates a notification's read/unread status, which is a reversible state change to existing data. This is a typical Write operation (modify data). The severity is low because toggling notification status has minimal blast radius—no data is deleted, no external systems are affected, and the change can be undone by toggling again.

From the tool's definition Tool name is 'planka_update_notification' and description states it 'Mark a notification as read or unread' — this modifies notification state reversibly without deleting or causing irreversible changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

planka_update_notification Rate-limited

planka_update_notification 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_notification": {
      "limits": [
        {
          "counter": "planka_update_notification_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_notification

What does the planka_update_notification tool do? +

Mark a notification as read or unread. 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_notification? +

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

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

Can I rate-limit planka_update_notification? +

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

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

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