Submit an audio file URL for transcription. Returns a job ID to poll with get_transcript. Example: transcribe_audio({ url:
AI agents invoke transcribe_audio to trigger actions in Descript Complete. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external transcription job/process by submitting a URL to a processing pipeline. It initiates an asynchronous operation (returning a job ID) rather than simply reading existing data or writing static content — it executes a processing workflow.
From the tool's definition Submit an audio file URL for transcription. Returns a job ID to poll with get_transcript.
Attacks that exploit this kind of access
Submit an audio file URL for transcription. Returns a job ID to poll with get_transcript. Example: transcribe_audio({ url:. It is categorised as a Execute tool in the Descript Complete MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Descript Complete MCP server in PolicyLayer and add a rule for transcribe_audio: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Descript Complete. Nothing to install.
transcribe_audio is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the transcribe_audio rule in your PolicyLayer 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 PolicyLayer policy for transcribe_audio. 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.
transcribe_audio is provided by the Descript Complete MCP server (josephtandle/descript-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →