create_track · Orpheus MCP: Risk & Policy

WHAT IT DOES

What create_track does on Orpheus

AI agents use create_track to create or update resources in Orpheus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Orpheus environment.

WHY IT NEEDS A POLICY

Why create_track needs a policy

Creating a new track in a music project is a reversible write operation—tracks can be deleted or modified. It does not execute arbitrary code, trigger external commands, or irreversibly destroy data. The effect is bounded to track creation within the REAPER project context.

From the tool's definition Tool description explicitly states 'Insert a named track', which creates new data (a track) in the REAPER project. Returns a stable GUID, indicating persistent creation of a new resource.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_track Rate-limited

create_track stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_track": {
      "limits": [
        {
          "counter": "create_track_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Orpheus, so you can run agents against it safely.

FAQ

Questions about create_track

What does the create_track tool do? +

Insert a named track and return its stable GUID (one composite bridge call). It is categorised as a Write tool in the Orpheus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_track? +

Register the Orpheus MCP server in PolicyLayer and add a rule for create_track: 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 Orpheus. Nothing to install.

What risk level is create_track? +

create_track is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_track? +

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

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

create_track is provided by the Orpheus MCP server (mal0ware/orpheus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.