List all notifications for the current user
AI agents call planka_list_notifications to retrieve information from Planka MCP Server for Claude without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries notification data without creating, modifying, deleting, or executing any operations. It is purely informational and read-only, presenting minimal security risk even if misused by an agent.
From the tool's definition Tool name includes 'list' and description states 'List all notifications for the current user' — a retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
List all notifications for the current user. It is categorised as a Read tool in the Planka MCP Server for Claude MCP Server, which means it retrieves data without modifying state.
Register the Planka MCP Server for Claude MCP server in PolicyLayer and add a rule for planka_list_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.
planka_list_notifications is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the planka_list_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.
Set action: deny in the PolicyLayer policy for planka_list_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.
planka_list_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →