Generate and add a bass track provided a chord progression.
AI agents use add_bass_track to create or update resources in Scythe MCP REAPER — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Scythe MCP REAPER environment.
This tool creates or adds new music data (a bass track with MIDI notes derived from chord progressions) to a REAPER project. This is a reversible modification—tracks and MIDI items can be deleted or edited afterward.
From the tool's definition Tool description states it will 'Generate and add a bass track' — a direct modification operation that creates new content within the DAW project.
Attacks that exploit this kind of access
Generate and add a bass track provided a chord progression. It is categorised as a Write tool in the Scythe MCP REAPER MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Scythe MCP REAPER MCP server in PolicyLayer and add a rule for add_bass_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 Scythe MCP REAPER. Nothing to install.
add_bass_track 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 add_bass_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.
Set action: deny in the PolicyLayer policy for add_bass_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.
add_bass_track is provided by the Scythe MCP REAPER MCP server (yura9011/scythe_mcp_reaper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →