stream_stop

What stream_stop does on Mcp Anything

AI agents invoke stream_stop to trigger actions in Mcp Anything. 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 stream_stop is rated High

This tool executes a command to halt a running stream, which is an action with external consequences. While not destructive (the stream can typically be restarted) or immediately dangerous, stopping a stream could interrupt dependent processes or workflows. This fits the Execute category: it runs an operation whose effects depend on what stream is active.

From the tool's definition Tool name 'stream_stop' and description 'Stop the current stream' indicate an action that terminates an ongoing operation. The imperative verb 'Stop' combined with 'current stream' suggests this tool triggers an external operation with side effects.

The rule that runs stream_stop safely

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stream_stop": {
      "limits": [
        {
          "counter": "stream_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about stream_stop