audio.transcribe.result
Retrieve the completed transcription text, word count, confidence score, detected language, and speaker labels (if diarization was enabled). Use transcript_id from submit (AssemblyAI)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/audio.transcribe.result.md
What audio.transcribe.result does on Apibase
AI agents call audio.transcribe.result to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
transcript_id | string | Yes | Transcript ID to get the completed transcription text for |
Parameters from the server's own tool schema.
Why audio.transcribe.result is rated Low
Fetches previously generated transcription data with no side effects or modifications.
From the tool's definition Retrieve completed transcription text, word count, confidence score, detected language
Attacks that exploit this kind of access
The rule that runs audio.transcribe.result safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For audio.transcribe.result, this is the rule to start with:
audio.transcribe.result is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every audio.transcribe.result call is checked against it from then on.
Questions about audio.transcribe.result
Retrieve the completed transcription text, word count, confidence score, detected language, and speaker labels (if diarization was enabled). Use transcript_id from submit (AssemblyAI). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
audio.transcribe.result accepts 1 parameter: transcript_id. Required: transcript_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for audio.transcribe.result: 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 Apibase. Nothing to install.
audio.transcribe.result is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the audio.transcribe.result 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 audio.transcribe.result. 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.
audio.transcribe.result is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue