This record as markdown: /tools/cowork-os/rhino.save-project.md
What rhino.save_project does on CoWork OS
AI agents use rhino.save_project to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.
Why rhino.save_project is rated Medium
The save operation modifies the project file state reversibly (the file can be reopened, edited, or reverted), making it a Write action rather than Destructive. The severity is medium because improper use could overwrite project work, but the operation is reversible through version control or backup restoration. Confidence is high given the explicit 'save' terminology and clear intent.
From the tool's definition Tool name and description: 'Save the active Rhino project' — this persists/modifies project state on disk.
Attacks that exploit this kind of access
The rule that runs rhino.save_project safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rhino.save_project, this is the rule to start with:
rhino.save_project 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.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every rhino.save_project call is checked against it from then on.
Questions about rhino.save_project
Save the active Rhino project. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CoWork OS MCP server in PolicyLayer and add a rule for rhino.save_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 CoWork OS. Nothing to install.
rhino.save_project 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 rhino.save_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 rhino.save_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.
rhino.save_project is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue