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. Allows you to modify how Mux validates playback requests with different user agents. Please see [Using User-Agent HTTP header for va...
Single-target operation
Part of the Mux MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use update_user_agent_video_playback_restrictions 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_user_agent_video_playback_restrictions 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.
tools:
update_user_agent_video_playback_restrictions:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Mux policy for all 98 tools.
Agents calling write-class tools like update_user_agent_video_playback_restrictions have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) 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. Allows you to modify how Mux validates playback requests with different user agents. Please see [Using User-Agent HTTP header for validation](https://docs.mux.com/guides/secure-video-playback#using-user-agent-http-header-for-validation) for more details on this feature. # Response Schema ```json { $ref: '#/$defs/playback_restriction_response', $defs: { playback_restriction_response: { type: 'object', properties: { data: { $ref: '#/$defs/playback_restriction' } }, required: [ 'data' ] }, playback_restriction: { type: 'object', properties: { id: { type: 'string', description: 'Unique identifier for the Playback Restriction. Max 255 characters.' }, created_at: { type: 'string', description: 'Time the Playback Restriction was created, defined as a Unix timestamp (seconds since epoch).' }, referrer: { type: 'object', description: 'A list of domains allowed to play your videos.', properties: { allow_no_referrer: { type: 'boolean', description: 'A boolean to determine whether to allow or deny HTTP requests without `Referer` HTTP request header. Playback requests coming from non-web/native applications like iOS, Android or smart TVs will not have a `Referer` HTTP header. Set this value to `true` to allow these playback requests.' }, allowed_domains: { type: 'array', description: 'List of domains allowed to play videos. Possible values are\n * `[]` Empty Array indicates deny video playback requests for all domains\n * `["*"]` A Single Wildcard `*` entry means allow video playback requests from any domain\n * `["*.example.com", "foo.com"]` A list of up to 10 domains or valid dns-style wildcards\n', items: { type: 'string' } } } }, updated_at: { type: 'string', description: 'Time the Playback Restriction was last updated, defined as a Unix timestamp (seconds since epoch).' }, user_agent: { type: 'object', description: 'Rules that control what user agents are allowed to play your videos. Please see [Using User-Agent HTTP header for validation](https://docs.mux.com/guides/secure-video-playback#using-user-agent-http-header-for-validation) for more details on this feature.', properties: { allow_high_risk_user_agent: { type: 'boolean', description: 'Whether or not to allow high risk user agents. The high risk user agents are defined by Mux.' }, allow_no_user_agent: { type: 'boolean', description: 'Whether or not to allow views without a `User-Agent` HTTP request header.' } } } }, required: [ 'id', 'created_at', 'referrer', 'updated_at', 'user_agent' ] } } } ```. 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.
Add a rule in your Intercept YAML policy under the tools section for update_user_agent_video_playback_restrictions. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mux MCP server.
update_user_agent_video_playback_restrictions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_user_agent_video_playback_restrictions 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 update_user_agent_video_playback_restrictions. 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.
update_user_agent_video_playback_restrictions 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