Drain accumulated events from a stream. Returns all changes since last read, then clears the buffer. Safe to call repeatedly.
AI agents call stream_read to retrieve information from TradingView MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves accumulated events from a stream and returns them without modifying underlying data or state. While it clears the buffer, this is a side effect of reading, not a destructive operation on user data. The operation is reversible (subsequent reads will accumulate new events), and there is no creation, modification, execution, or financial impact.
From the tool's definition Tool name 'stream_read' and description 'Drain accumulated events from a stream. Returns all changes since last read, then clears the buffer.' explicitly indicates reading/retrieving data with no side effects beyond buffer clearing.
Attacks that exploit this kind of access
Drain accumulated events from a stream. Returns all changes since last read, then clears the buffer. Safe to call repeatedly. It is categorised as a Read tool in the TradingView MCP MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP server in PolicyLayer and add a rule for stream_read: 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.
stream_read is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the stream_read 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.
Set action: deny in the PolicyLayer policy for stream_read. 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.
stream_read 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →