generate_drums_json · Scythe MCP REAPER MCP: Risk & Policy

WHAT IT DOES

What generate_drums_json does on Scythe MCP REAPER

AI agents use generate_drums_json 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.

WHY IT NEEDS A POLICY

Why generate_drums_json needs a policy

This tool creates new data (drum pattern JSON) that will be written to the DAW project when combined with add_notes. While it doesn't directly execute destructive operations or move to higher severity categories, it modifies the composition state.

From the tool's definition Tool generates drum pattern data in JSON format that is explicitly stated to be 'used with add_notes', indicating it creates or modifies musical data within the REAPER DAW session.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_drums_json Rate-limited

generate_drums_json 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": {
    "generate_drums_json": {
      "limits": [
        {
          "counter": "generate_drums_json_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 Scythe MCP REAPER, so you can run agents against it safely.

FAQ

Questions about generate_drums_json

What does the generate_drums_json tool do? +

Generate drum pattern data (JSON) to be used with add_notes. 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.

How do I enforce a policy on generate_drums_json? +

Register the Scythe MCP REAPER MCP server in PolicyLayer and add a rule for generate_drums_json: 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.

What risk level is generate_drums_json? +

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

Can I rate-limit generate_drums_json? +

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

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

generate_drums_json 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.