Low Risk

static_rendition_video_playback

Fetch a static rendition (usually an MP4 or M4A file) of the specified video asset. [MP4 Support](https://docs.mux.com/guides/enable-static-mp4-renditions) must be enabled on the asset before using these URLs.

Accepts file system path (FILENAME); Handles credentials or secrets (TOKEN)

Part of the Mux MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@mux/mcp Read Risk 2/5

AI agents call static_rendition_video_playback 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 static_rendition_video_playback 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.

com-mux-mcp.yaml
tools:
  static_rendition_video_playback:
    rules:
      - action: allow

See the full Mux policy for all 98 tools.

Tool Name static_rendition_video_playback
Category Read
MCP Server Mux MCP Server
Risk Level Low

View all 98 tools →

Agents calling read-class tools like static_rendition_video_playback have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the static_rendition_video_playback tool do? +

Fetch a static rendition (usually an MP4 or M4A file) of the specified video asset. [MP4 Support](https://docs.mux.com/guides/enable-static-mp4-renditions) must be enabled on the asset before using these URLs.. It is categorised as a Read tool in the Mux MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on static_rendition_video_playback? +

Add a rule in your Intercept YAML policy under the tools section for static_rendition_video_playback. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mux MCP server.

What risk level is static_rendition_video_playback? +

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

Can I rate-limit static_rendition_video_playback? +

Yes. Add a rate_limit block to the static_rendition_video_playback 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.

How do I block static_rendition_video_playback completely? +

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

static_rendition_video_playback 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.

Enforce policies on Mux

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.