stopStreamingTool · Beep MCP Server MCP: Risk & Policy

WHAT IT DOES

What stopStreamingTool does on Beep MCP Server

AI agents invoke stopStreamingTool to trigger actions in Beep MCP Server. 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 stopStreamingTool needs a policy

Stopping a streaming session is an external operation that triggers a state change on the Beep network. While it may have financial implications (ending a payment stream), the primary action is executing a stop command on a running session. It is not purely destructive (data isn't deleted) nor directly a financial transaction, but it does affect an ongoing financial stream, making it a high-severity Execute action.

From the tool's definition 'Stops the streaming for the given invoice' — terminates an active streaming session tied to a financial invoice

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stopStreamingTool Rate-limited

stopStreamingTool 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": {
    "stopStreamingTool": {
      "limits": [
        {
          "counter": "stopstreamingtool_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 Beep MCP Server, so you can run agents against it safely.

FAQ

Questions about stopStreamingTool

What does the stopStreamingTool tool do? +

Stops the streaming for the given invoice. It is categorised as a Execute tool in the Beep MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stopStreamingTool? +

Register the Beep MCP Server MCP server in PolicyLayer and add a rule for stopStreamingTool: 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 Beep MCP Server. Nothing to install.

What risk level is stopStreamingTool? +

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

Can I rate-limit stopStreamingTool? +

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

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

stopStreamingTool is provided by the Beep MCP Server MCP server (lamdanghoang/beep-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.