transcription_status
Check whether local FFmpeg, whisper.cpp, and a configured model are ready.
This record as markdown: /tools/cutpilot/transcription-status.md
What transcription_status does on Cutpilot
AI agents call transcription_status to retrieve information from Cutpilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why transcription_status is rated Low
This tool retrieves and reports the readiness status of local components. It performs no side effects, does not modify data, execute code, delete anything, or move money. It is a pure information-retrieval operation, fitting squarely into the Read category with low severity since misuse would only expose status information about system dependencies.
From the tool's definition Tool name and description: 'Check whether local FFmpeg, whisper.cpp, and a configured model are ready' — this is a status check operation that queries the state of local dependencies without modifying or executing them.
Attacks that exploit this kind of access
The rule that runs transcription_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cutpilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transcription_status, this is the rule to start with:
transcription_status 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 Cutpilot, apply this rule, and every transcription_status call is checked against it from then on.
Questions about transcription_status
Check whether local FFmpeg, whisper.cpp, and a configured model are ready. It is categorised as a Read tool in the Cutpilot MCP Server, which means it retrieves data without modifying state.
Register the Cutpilot MCP server in PolicyLayer and add a rule for transcription_status: 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 Cutpilot. Nothing to install.
transcription_status 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 transcription_status 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 transcription_status. 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.
transcription_status is provided by the Cutpilot MCP server (Hellotravisss/cutpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cutpilot, and thousands of servers like it.
This server
Across the catalogue