planka_read_all_notifications

WHAT IT DOES

What planka_read_all_notifications does on Planka MCP Server for Claude

AI agents use planka_read_all_notifications 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_read_all_notifications needs a policy

This tool modifies the state of notifications by marking them all as read. While it changes data, this is a reversible/soft state change (notifications could be unmarked), not destructive. It has minimal blast radius as it only affects notification read-status, not core project data.

From the tool's definition Mark all notifications as read

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

planka_read_all_notifications Rate-limited

planka_read_all_notifications 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_read_all_notifications": {
      "limits": [
        {
          "counter": "planka_read_all_notifications_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_read_all_notifications

What does the planka_read_all_notifications tool do? +

Mark all notifications as read. 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_read_all_notifications? +

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

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

Can I rate-limit planka_read_all_notifications? +

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

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

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