create_drum_pattern
AI agents use create_drum_pattern 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 'create_' prefix and the pattern of similar sibling tools confirm this creates new data (a drum pattern) within the music project. This is reversible (patterns can be deleted/modified), so it falls under Write rather than Execute or Destructive. The description is empty, which lowers confidence slightly, but the naming convention and server context are clear.
From the tool's definition Tool name 'create_drum_pattern' indicates creation of new content (drum pattern). Context shows sibling tools like 'create_chord_progression', 'demo_edm_project', and 'bounce_stems' that generate or write music data to the REAPER project.
Documented attack patterns abuse exactly the kind of access create_drum_pattern 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_drum_pattern:
{
"version": "1",
"default": "deny",
"tools": {
"create_drum_pattern": {
"limits": [
{
"counter": "create_drum_pattern_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_drum_pattern 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_drum_pattern. 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_drum_pattern: 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_drum_pattern 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_drum_pattern 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_drum_pattern. 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_drum_pattern 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.