transcription_status

Check whether local FFmpeg, whisper.cpp, and a configured model are ready.

SERVERCutpilot SOURCEHellotravisss/cutpilot

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cutpilot/transcription-status.md

WHAT IT DOES

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.

RISK

Why transcription_status is rated Low

Even though transcription_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

transcription_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transcription_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about transcription_status

What does the transcription_status tool do? +

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.

How do I enforce a policy on transcription_status? +

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.

What risk level is transcription_status? +

transcription_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit transcription_status? +

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.

How do I block transcription_status completely? +

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.

What MCP server provides transcription_status? +

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.

KEEP EXPLORING

More on Cutpilot, and thousands of servers like it.

This server

All 219 Cutpilot tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →