Medium Risk

update_new_asset_settings_static_renditions_video_live_streams

Updates a live stream's static renditions settings for new assets. Further assets made via this live stream will create static renditions per the settings provided. You must provide all static renditions desired.

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

@mux/mcp Write Risk 2/5

AI agents use update_new_asset_settings_static_renditions_video_live_streams to create or modify resources in Mux. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call update_new_asset_settings_static_renditions_video_live_streams repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mux.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

com-mux-mcp.yaml
tools:
  update_new_asset_settings_static_renditions_video_live_streams:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Mux policy for all 98 tools.

Tool Name update_new_asset_settings_static_renditions_video_live_streams
Category Write
MCP Server Mux MCP Server
Risk Level Medium

View all 98 tools →

Agents calling write-class tools like update_new_asset_settings_static_renditions_video_live_streams 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 Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the update_new_asset_settings_static_renditions_video_live_streams tool do? +

Updates a live stream's static renditions settings for new assets. Further assets made via this live stream will create static renditions per the settings provided. You must provide all static renditions desired.. It is categorised as a Write tool in the Mux MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_new_asset_settings_static_renditions_video_live_streams? +

Add a rule in your Intercept YAML policy under the tools section for update_new_asset_settings_static_renditions_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.

What risk level is update_new_asset_settings_static_renditions_video_live_streams? +

update_new_asset_settings_static_renditions_video_live_streams is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_new_asset_settings_static_renditions_video_live_streams? +

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

How do I block update_new_asset_settings_static_renditions_video_live_streams completely? +

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

What MCP server provides update_new_asset_settings_static_renditions_video_live_streams? +

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

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.