AI agents invoke transport_stop to trigger actions in AudacityMCP. 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 a command that controls Audacity's transport state by stopping playback or recording. While the action itself is reversible and has minimal blast radius (the user can simply resume playback or re-record), it falls under Execute rather than Write because it triggers an external operation whose effects depend on system state at invocation time.
From the tool's definition Tool name 'transport_stop' and description 'Stop playback or recording' indicate it triggers an external operation in Audacity that halts an active process.
Documented attack patterns abuse exactly the kind of access transport_stop gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AudacityMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for transport_stop:
{
"version": "1",
"default": "deny",
"tools": {
"transport_stop": {
"limits": [
{
"counter": "transport_stop_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}transport_stop 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.
Stop playback or recording. It is categorised as a Execute tool in the AudacityMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Audacity MCP server in PolicyLayer and add a rule for transport_stop: 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 AudacityMCP. Nothing to install.
transport_stop 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 transport_stop 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 transport_stop. 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.
transport_stop is provided by the Audacity MCP server (xdarkzx/audacity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 131 AudacityMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
131 AudacityMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.