stream_stop · TradingView MCP: Risk & Policy

WHAT IT DOES

What stream_stop does on TradingView MCP

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

While not creating or modifying persistent data (Write), this tool executes a command that halts an ongoing operation and deallocates resources. This is an Execute-class action because it triggers external behavior with side effects that depend on which stream is targeted. It is not Destructive because stopping a stream is reversible (a new stream can be started).

From the tool's definition The tool description states 'Stop a stream and release its buffer', which indicates it triggers an external operation (stopping a running stream) and manages system resources (buffer release).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stream_stop Rate-limited

stream_stop 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": {
    "stream_stop": {
      "limits": [
        {
          "counter": "stream_stop_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 TradingView MCP, so you can run agents against it safely.

FAQ

Questions about stream_stop

What does the stream_stop tool do? +

Stop a stream and release its buffer. Always call this when done to free resources. It is categorised as a Execute tool in the TradingView MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stream_stop? +

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

What risk level is stream_stop? +

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

Can I rate-limit stream_stop? +

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

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

stream_stop is provided by the TradingView MCP server (ulianbass/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.