Stop the running Whisper audio capture loop. Flushes and transcribes the final audio chunk before stopping.
AI agents invoke pilotgentic_stop_transcription to trigger actions in PilotGentic. 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.
This tool triggers an external transcription service (Whisper) and controls an active audio capture loop. While not destructive (the audio capture can be restarted), it executes external operations with effects dependent on the current state of the audio loop and captured audio.
From the tool's definition The tool description states it 'Stop[s] the running Whisper audio capture loop' and 'Flushes and transcribes the final audio chunk before stopping.' This invokes an external operation (Whisper audio transcription) and modifies system state (stopping an active…
Attacks that exploit this kind of access
Stop the running Whisper audio capture loop. Flushes and transcribes the final audio chunk before stopping. It is categorised as a Execute tool in the PilotGentic MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PilotGentic MCP server in PolicyLayer and add a rule for pilotgentic_stop_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 PilotGentic. Nothing to install.
pilotgentic_stop_transcription 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 pilotgentic_stop_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 pilotgentic_stop_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.
pilotgentic_stop_transcription is provided by the PilotGentic MCP server (@pilotgentic/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →