planka_test_notification_service

WHAT IT DOES

What planka_test_notification_service does on Planka MCP Server for Claude

AI agents invoke planka_test_notification_service to trigger actions in Planka MCP Server for Claude. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why planka_test_notification_service needs a policy

This tool triggers an external operation — sending a test message to a notification service. It doesn't just read or write data; it actively dispatches a notification to an external system, which is an outbound operation with side effects. This falls under Execute as it triggers external operations.

From the tool's definition Send a test message to a notification service

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

planka_test_notification_service Rate-limited

planka_test_notification_service stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_test_notification_service": {
      "limits": [
        {
          "counter": "planka_test_notification_service_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_test_notification_service

What does the planka_test_notification_service tool do? +

Send a test message to a notification service. It is categorised as a Execute tool in the Planka MCP Server for Claude MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on planka_test_notification_service? +

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

planka_test_notification_service is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit planka_test_notification_service? +

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

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

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