Get project info (name, BPM, time sig, tracks, length, markers, render settings).
AI agents call project_get_info to retrieve information from ReaperMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns information about a REAPER project's properties. It performs no data modification, deletion, code execution, or financial transaction. It is a straightforward retrieval operation that fits the 'Read' category.
From the tool's definition Tool name is 'project_get_info' and description states it 'Get[s] project info (name, BPM, time sig, tracks, length, markers, render settings)' — purely retrieving metadata about an existing project with no modification or side effects.
Documented attack patterns abuse exactly the kind of access project_get_info 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 project_get_info:
{
"version": "1",
"default": "deny",
"tools": {
"project_get_info": {}
}
}project_get_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get project info (name, BPM, time sig, tracks, length, markers, render settings). It is categorised as a Read tool in the ReaperMCP MCP Server, which means it retrieves data without modifying state.
Register the Reaper MCP server in PolicyLayer and add a rule for project_get_info: 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.
project_get_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the project_get_info 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 project_get_info. 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.
project_get_info 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.