Stops the currently playing audio (if any) and clears all pending TTS requests from the queue.
AI agents invoke tts_stop_playback_and_clear_queue to trigger actions in MCP TTS Server. 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 executes commands that affect the state of a media playback system and its queue. While not destructive (no data is permanently deleted or overwritten), it irreversibly interrupts ongoing operations and discards queued requests. The impact is operational rather than data-based, making it Execute rather than Destructive.
From the tool's definition Tool description states it 'Stops the currently playing audio (if any) and clears all pending TTS requests from the queue' — active operations that trigger immediate effects on a running system.
Documented attack patterns abuse exactly the kind of access tts_stop_playback_and_clear_queue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP TTS Server, and nothing reaches the server without passing your rules. This is the rule we recommend for tts_stop_playback_and_clear_queue:
{
"version": "1",
"default": "deny",
"tools": {
"tts_stop_playback_and_clear_queue": {
"limits": [
{
"counter": "tts_stop_playback_and_clear_queue_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}tts_stop_playback_and_clear_queue 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.
Free to start. No card required.
Stops the currently playing audio (if any) and clears all pending TTS requests from the queue. It is categorised as a Execute tool in the MCP TTS Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP TTS Server MCP server in PolicyLayer and add a rule for tts_stop_playback_and_clear_queue: 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 MCP TTS Server. Nothing to install.
tts_stop_playback_and_clear_queue 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 tts_stop_playback_and_clear_queue 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 tts_stop_playback_and_clear_queue. 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.
tts_stop_playback_and_clear_queue is provided by the MCP TTS Server MCP server (kristofferv98/mcp_tts_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP TTS Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 MCP TTS Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.