create_chord_progression
AI agents use create_chord_progression 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.
The tool creates new musical data within a REAPER project, which is reversible (can be undone). This qualifies as Write rather than Read (it generates content, not just retrieves it) or Execute (not running arbitrary code). The empty description lowers confidence slightly, but the tool name and server context strongly suggest data creation.
From the tool's definition Tool name 'create_chord_progression' indicates creation of musical data (a chord progression). Sibling tools like 'create_drum_pattern' and 'bounce_stems' suggest this server modifies REAPER projects by generating or writing musical content.
Documented attack patterns abuse exactly the kind of access create_chord_progression 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 create_chord_progression:
{
"version": "1",
"default": "deny",
"tools": {
"create_chord_progression": {
"limits": [
{
"counter": "create_chord_progression_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_chord_progression 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.
create_chord_progression. 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 create_chord_progression: 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.
create_chord_progression 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 create_chord_progression 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 create_chord_progression. 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.
create_chord_progression 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.