start-notification-stream

What start-notification-stream does on Mcp Test Servers

AI agents invoke start-notification-stream to trigger actions in Mcp Test Servers. 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 start-notification-stream is rated High

This tool executes an action with side effects that runs continuously or periodically, rather than simply retrieving data. Notifications are sent outbound, affecting external systems or state. The tool's behavior depends on the runtime environment—if misconfigured or triggered without proper authorization, it could spam users, trigger alerts, or disturb system stability.

From the tool's definition Tool 'start-notification-stream' with description 'Starts sending periodic notifications' initiates an ongoing external operation (a notification stream) whose effects persist and cannot be trivially stopped by the user.

The rule that runs start-notification-stream safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Test Servers, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For start-notification-stream, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start-notification-stream": {
      "limits": [
        {
          "counter": "start-notification-stream_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about start-notification-stream