Save the current project. Returns project info confirming the save.
AI agents use project_save 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 tool creates or modifies data reversibly by saving project state. While the operation itself is not destructive (it can be undone by reverting to a previous save), it does alter the persisted project file. This represents a Write-category action. Severity is medium because misuse could overwrite unsaved work or corrupt the project state, but the action is reversible through version control or undo mechanisms.
From the tool's definition Tool name is 'project_save' and description states 'Save the current project.' This is a write operation that modifies persistent state by committing the current project state to disk.
Documented attack patterns abuse exactly the kind of access project_save 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_save:
{
"version": "1",
"default": "deny",
"tools": {
"project_save": {
"limits": [
{
"counter": "project_save_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}project_save 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.
Save the current project. Returns project info confirming the save. 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 project_save: 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_save 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 project_save 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_save. 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_save 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.