test_notification · Run402 MCP: Risk & Policy

WHAT IT DOES

What test_notification does on Run402

AI agents invoke test_notification to trigger actions in Run402. 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 test_notification needs a policy

The tool actively triggers a real notification through the system pipeline, which constitutes executing an external operation. While marked as a test (is_test=true) and rate-limited, it still causes side effects in external systems (notification delivery, audit row creation).

From the tool's definition 'Trigger a real test notification' and 'Verifies the full pipeline end-to-end' indicate this runs an actual external operation (sending a notification through the full pipeline), not just reading data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_notification Rate-limited

test_notification 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": {
    "test_notification": {
      "limits": [
        {
          "counter": "test_notification_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 Run402, so you can run agents against it safely.

FAQ

Questions about test_notification

What does the test_notification tool do? +

Trigger a real test notification (audit row marked is_test=true). Rate-limited per wallet at 1/min. Verifies the full pipeline end-to-end. It is categorised as a Execute tool in the Run402 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_notification? +

Register the Run402 MCP server in PolicyLayer and add a rule for test_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 Run402. Nothing to install.

What risk level is test_notification? +

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

Can I rate-limit test_notification? +

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

Set action: deny in the PolicyLayer policy for test_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 test_notification? +

test_notification is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.