AI agents use track_rename to create or update resources in ReaperMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ReaperMCP environment.
Renaming a track is a reversible write operation that modifies metadata only. It does not delete data (not Destructive), execute arbitrary code (not Execute), move money (not Financial), or retrieve data without side effects (not Read). The operation is easily undone by renaming again, and the blast radius of misuse is low—a track with an undesired name causes no loss of audio or project integrity.
From the tool's definition Tool name 'track_rename' and description 'Rename a track' indicate modification of track metadata without destructive consequences or side effects beyond the rename operation itself.
Documented attack patterns abuse exactly the kind of access track_rename gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ReaperMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for track_rename:
{
"version": "1",
"default": "deny",
"tools": {
"track_rename": {
"limits": [
{
"counter": "track_rename_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}track_rename 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.
Free to start. No card required.
Rename a track. It is categorised as a Write tool in the ReaperMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Reaper MCP server in PolicyLayer and add a rule for track_rename: 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 ReaperMCP. Nothing to install.
track_rename is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the track_rename 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 track_rename. 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.
track_rename is provided by the Reaper MCP server (xdarkzx/reaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ReaperMCP, 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.
138 ReaperMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.