Low Risk

retrieve_video_transcription_vocabularies

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 a Transcription Vocabulary that has previously been created. Supply the unique Transcription Vocabulary ID a...

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

@mux/mcp Read

AI agents call retrieve_video_transcription_vocabularies 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_video_transcription_vocabularies 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:
  retrieve_video_transcription_vocabularies:
    rules:
      - action: allow

See the full Mux policy for all 98 tools.

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

View all 98 tools →

Agents calling read-class tools like retrieve_video_transcription_vocabularies 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 retrieve_video_transcription_vocabularies tool do? +

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 a Transcription Vocabulary that has previously been created. Supply the unique Transcription Vocabulary ID and Mux will return the corresponding Transcription Vocabulary information. The same information is returned when creating a Transcription Vocabulary. # Response Schema ```json { $ref: '#/$defs/transcription_vocabulary_response', $defs: { transcription_vocabulary_response: { type: 'object', properties: { data: { $ref: '#/$defs/transcription_vocabulary' } }, required: [ 'data' ] }, transcription_vocabulary: { type: 'object', properties: { id: { type: 'string', description: 'Unique identifier for the Transcription Vocabulary' }, created_at: { type: 'string', description: 'Time the Transcription Vocabulary was created, defined as a Unix timestamp (seconds since epoch).' }, updated_at: { type: 'string', description: 'Time the Transcription Vocabulary was updated, defined as a Unix timestamp (seconds since epoch).' }, name: { type: 'string', description: 'The user-supplied name of the Transcription Vocabulary.' }, passthrough: { type: 'string', description: 'Arbitrary user-supplied metadata set for the Transcription Vocabulary. Max 255 characters.' }, phrases: { type: 'array', description: 'Phrases, individual words, or proper names to include in the Transcription Vocabulary. When the Transcription Vocabulary is attached to a live stream\'s `generated_subtitles` configuration, the probability of successful speech recognition for these words or phrases is boosted.', items: { type: 'string', description: 'A phrase or word belonging to a Transcription Vocabulary.' } } }, required: [ 'id', 'created_at', 'updated_at' ] } } } ```. 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 retrieve_video_transcription_vocabularies? +

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

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

Can I rate-limit retrieve_video_transcription_vocabularies? +

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

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

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