openai_create_transcription
Transcribe audio to text using OpenAI Whisper.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/openai-create-transcription.md
What openai_create_transcription does on UnClick
AI agents use openai_create_transcription to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
model | string | — | Transcription model (default: whisper-1) |
prompt | string | — | |
api_key | string | Yes | |
filename | string | — | |
language | string | — | ISO-639-1 language code (optional) |
audio_url | string | Yes | URL of the audio file to transcribe |
temperature | number | — | |
response_format | string | — | json, text, srt, verbose_json, vtt (default: json) |
Parameters from the server's own tool schema.
Why openai_create_transcription is rated Medium
An AI agent can call openai_create_transcription faster than any human can review: one bad instruction and it creates or modifies resources in UnClick by the hundred, each call as confident as the last.
Risk signalsAccepts file system path (filename) · Handles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs openai_create_transcription safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openai_create_transcription, this is the rule to start with:
openai_create_transcription stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every openai_create_transcription call is checked against it from then on.
Questions about openai_create_transcription
Transcribe audio to text using OpenAI Whisper. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
openai_create_transcription accepts 8 parameters: model, prompt, api_key, filename, language, audio_url, temperature, response_format. Required: api_key, audio_url. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for openai_create_transcription: 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 UnClick. Nothing to install.
openai_create_transcription 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 openai_create_transcription 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 openai_create_transcription. 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.
openai_create_transcription is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue