AI agents call demo_edm_project as a supporting operation in ReaperMCP workflows.
With no description, the exact behavior is unknown. The name suggests it may create or write a demo project (Write), but it could also execute a series of actions. Confidence is low due to absent description; defaulting to Other with medium severity given the broad music production context and potential for significant project modifications.
From the tool's definition Tool description is empty and uninformative; name 'demo_edm_project' suggests creating a demonstration EDM project in REAPER.
Documented attack patterns abuse exactly the kind of access demo_edm_project 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 demo_edm_project:
{
"version": "1",
"default": "deny",
"tools": {
"demo_edm_project": {
"limits": [
{
"counter": "demo_edm_project_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}demo_edm_project gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
demo_edm_project. It is categorised as a Other tool in the ReaperMCP MCP Server, which means it performs auxiliary operations.
Register the Reaper MCP server in PolicyLayer and add a rule for demo_edm_project: 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.
demo_edm_project is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the demo_edm_project 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 demo_edm_project. 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.
demo_edm_project 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.