When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance. Only omit if you're sure you don't need the data. Retrieves the details of the simulcast target created for the parent live stream. Supply the unique live stream ID and simulcast targ...
Part of the Mux MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call retrieve_simulcast_target_video_live_streams to retrieve information from Mux without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though retrieve_simulcast_target_video_live_streams only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
retrieve_simulcast_target_video_live_streams:
rules:
- action: allowSee the full Mux policy for all 98 tools.
Agents calling read-class tools like retrieve_simulcast_target_video_live_streams have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance. Only omit if you're sure you don't need the data. Retrieves the details of the simulcast target created for the parent live stream. Supply the unique live stream ID and simulcast target ID that was returned in the response of create simulcast target request, and Mux will return the corresponding information. # Response Schema ```json { type: 'object', properties: { data: { $ref: '#/$defs/simulcast_target' } }, required: [ 'data' ], $defs: { simulcast_target: { type: 'object', properties: { id: { type: 'string', description: 'ID of the Simulcast Target' }, status: { type: 'string', description: 'The current status of the simulcast target. See Statuses below for detailed description.\n * `idle`: Default status. When the parent live stream is in disconnected status, simulcast targets will be idle state.\n * `starting`: The simulcast target transitions into this state when the parent live stream transition into connected state.\n * `broadcasting`: The simulcast target has successfully connected to the third party live streaming service and is pushing video to that service.\n * `errored`: The simulcast target encountered an error either while attempting to connect to the third party live streaming service, or mid-broadcasting. When a simulcast target has this status it will have an `error_severity` field with more details about the error.', enum: [ 'idle', 'starting', 'broadcasting', 'errored' ] }, url: { type: 'string', description: 'The RTMP(s) or SRT endpoint for a simulcast destination.\n* For RTMP(s) destinations, this should include the application name for the third party live streaming service, for example: `rtmp://live.example.com/app`.\n* For SRT destinations, this should be a fully formed SRT connection string, for example: `srt://srt-live.example.com:1234?streamid={stream_key}&passphrase={srt_passphrase}`.\n\nNote: SRT simulcast targets can only be used when an source is connected over SRT.\n' }, error_severity: { type: 'string', description: 'The severity of the error encountered by the simulcast target.\nThis field is only set when the simulcast target is in the `errored` status.\nSee the values of severities below and their descriptions.\n * `normal`: The simulcast target encountered an error either while attempting to connect to the third party live streaming service, or mid-broadcasting. A simulcast may transition back into the broadcasting state if a connection with the service can be re-established.\n * `fatal`: The simulcast target is incompatible with the current input to the parent live stream. No further attempts to this simulcast target will be made for the current live stream asset.', enum: [ 'normal', 'fatal' ] }, passthrough: { type: 'string', description: 'Arbitrary user-supplied metadata set when creating a simulcast target.' }, stream_key: { type: 'string', description: 'Stream Key represents a stream identifier on the third party live streaming service to send the parent live stream to. Only used for RTMP(s) simulcast destinations.' } }, required: [ 'id', 'status', 'url' ] } } } ```. It is categorised as a Read tool in the Mux MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for retrieve_simulcast_target_video_live_streams. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mux MCP server.
retrieve_simulcast_target_video_live_streams 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 retrieve_simulcast_target_video_live_streams rule in your Intercept 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 Intercept policy for retrieve_simulcast_target_video_live_streams. 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.
retrieve_simulcast_target_video_live_streams is provided by the Mux MCP server (@mux/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept