stream_execution

Get real-time streaming information for a workflow execution. Returns the SSE endpoint URL and authentication details for connecting to the execution stream.

SERVERFlowDot MCP Server SOURCEflowdot-llc/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/flowdot-llc-mcp-server/stream-execution.md

WHAT IT DOES

What stream_execution does on FlowDot MCP Server

AI agents call stream_execution to retrieve information from FlowDot MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why stream_execution is rated Low

This tool queries and returns data about an existing workflow execution stream. It has no side effects—it does not modify workflow state, execute new operations, delete data, or trigger external actions. The information returned (SSE endpoint and auth details) enables consumption of existing stream data. This is a passive Read operation with minimal blast radius.

From the tool's definition Tool retrieves real-time streaming information and returns connection details ('Get real-time streaming information', 'Returns the SSE endpoint URL and authentication details'); no modification, deletion, or external execution is performed.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stream_execution safely

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

stream_execution Allowed

stream_execution is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stream_execution": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every stream_execution call is checked against it from then on.

FAQ

Questions about stream_execution

What does the stream_execution tool do? +

Get real-time streaming information for a workflow execution. Returns the SSE endpoint URL and authentication details for connecting to the execution stream. It is categorised as a Read tool in the FlowDot MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on stream_execution? +

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

What risk level is stream_execution? +

stream_execution is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit stream_execution? +

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

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

stream_execution is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FlowDot MCP Server, and thousands of servers like it.

This server

All 207 FlowDot MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →