libi.analysis_transcribe_audio
Run the full transcript pipeline server-side: extract audio, chunk if needed (10-min default), transcribe per chunk, save each chunk row, auto-aggregate. Provider defaults to local Whisper (free); pass provider:
This record as markdown: /tools/libi/libi.analysis-transcribe-audio.md
What libi.analysis_transcribe_audio does on Libi
AI agents invoke libi.analysis_transcribe_audio to trigger actions in Libi. 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.
Why libi.analysis_transcribe_audio is rated High
Executes audio processing pipeline with side effects; creates transcript data files server-side.
From the tool's definition transcribe, extract audio, chunk, save, aggregate server-side
Attacks that exploit this kind of access
The rule that runs libi.analysis_transcribe_audio safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Libi, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For libi.analysis_transcribe_audio, this is the rule to start with:
libi.analysis_transcribe_audio stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Libi, apply this rule, and every libi.analysis_transcribe_audio call is checked against it from then on.
Questions about libi.analysis_transcribe_audio
Run the full transcript pipeline server-side: extract audio, chunk if needed (10-min default), transcribe per chunk, save each chunk row, auto-aggregate. Provider defaults to local Whisper (free); pass provider:. It is categorised as a Execute tool in the Libi MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Libi MCP server in PolicyLayer and add a rule for libi.analysis_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 Libi. Nothing to install.
libi.analysis_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 libi.analysis_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 libi.analysis_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.
libi.analysis_transcribe_audio is provided by the Libi MCP server (Nagellabs/libi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Libi, and thousands of servers like it.
This server
Across the catalogue