save_document_as
Save the current Rhino document to a new file path.
This record as markdown: /tools/hybridlabor-api-aos/save-document-as.md
What save_document_as does on Aos
AI agents use save_document_as to create or update resources in Aos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aos environment.
Why save_document_as is rated Medium
The tool creates or modifies files by saving a document to a specified path. While it doesn't delete existing data, it can overwrite files at the target path if they exist, making it a Write operation rather than Read. Severity is medium because misuse could result in unintended file creation/overwrites, but this is reversible (the original file persists unless explicitly overwritten).
From the tool's definition Tool name 'save_document_as' and description explicitly indicates it saves/writes the current Rhino document to a new file path. This is a file write operation.
Attacks that exploit this kind of access
The rule that runs save_document_as safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For save_document_as, this is the rule to start with:
save_document_as 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 Aos, apply this rule, and every save_document_as call is checked against it from then on.
Questions about save_document_as
Save the current Rhino document to a new file path. It is categorised as a Write tool in the Aos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aos MCP server in PolicyLayer and add a rule for save_document_as: 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 Aos. Nothing to install.
save_document_as 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 save_document_as 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 save_document_as. 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.
save_document_as is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue