High Risk →

cursor_set_position

Move the cursor to a specific time position.

How to control cursor_set_position ↓

AI agents invoke cursor_set_position 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.

High Risk

This tool triggers an action in Audacity (moving the playback/edit cursor), which constitutes an external operation affecting the state of the application. It is not a pure read, but rather a UI/state manipulation that changes the editing context. Misuse could disrupt ongoing editing sessions or cause unintended operations at wrong positions.

From the tool's definition Move the cursor to a specific time position

Documented attack patterns abuse exactly the kind of access cursor_set_position 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_set_position:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cursor_set_position": {
      "limits": [
        {
          "counter": "cursor_set_position_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

cursor_set_position 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.

  1. Create a free account and register AudacityMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the cursor_set_position tool do? +

Move the cursor to a specific time position. 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.

How do I enforce a policy on cursor_set_position? +

Register the Audacity MCP server in PolicyLayer and add a rule for cursor_set_position: 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.

What risk level is cursor_set_position? +

cursor_set_position is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit cursor_set_position? +

Yes. Add a rate_limit block to the cursor_set_position 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 cursor_set_position completely? +

Set action: deny in the PolicyLayer policy for cursor_set_position. 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 cursor_set_position? +

cursor_set_position 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.

Enforce policy on every AudacityMCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.