stream
AI agents call stream as a supporting operation in HoloViz MCP Server workflows.
The description is empty and uninformative, making it impossible to accurately classify. 'Stream' could refer to streaming data (Read), streaming output (Execute), or something else entirely. In the context of a HoloViz visualization server, it likely streams data or updates to a visualization, which could be Read or Write, but confidence is very low. Defaulting to Other due to insufficient information.
From the tool's definition Tool name is 'stream' with empty description. No information about what the tool does beyond its name.
Attacks that exploit this kind of access
stream. It is categorised as a Other tool in the HoloViz MCP Server MCP Server, which means it performs auxiliary operations.
Register the HoloViz MCP Server MCP server in PolicyLayer and add a rule for stream: 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 HoloViz MCP Server. Nothing to install.
stream is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the stream 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. 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 is provided by the HoloViz MCP Server MCP server (sumayabee/holoviz-mcp-server). 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 →