Move the cursor to the end of the project (last audio).
AI agents invoke cursor_to_project_end 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 triggers a UI/playback action in Audacity — moving the cursor position — which is an external operation affecting application state. It doesn't read data or write/modify audio content, but it does execute a navigation command within Audacity. Severity is low as it has minimal blast radius; it only repositions the playback cursor.
From the tool's definition Move the cursor to the end of the project (last audio)
Documented attack patterns abuse exactly the kind of access cursor_to_project_end 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 cursor_to_project_end:
{
"version": "1",
"default": "deny",
"tools": {
"cursor_to_project_end": {
"limits": [
{
"counter": "cursor_to_project_end_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} cursor_to_project_end 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.
Move the cursor to the end of the project (last audio). 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 cursor_to_project_end: 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.
cursor_to_project_end 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 cursor_to_project_end 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 cursor_to_project_end. 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.
cursor_to_project_end 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.