superdoc_save
Save the document to disk. Writes to the original path unless "out" is specified.
This record as markdown: /tools/superdoc-mcp/superdoc-save.md
What superdoc_save does on Superdoc
AI agents use superdoc_save to create or update resources in Superdoc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Superdoc environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
out | string | — | Save to a different file path instead of the original. |
session_id | string | Yes | Session ID from superdoc_open. |
Parameters from the server's own tool schema.
Why superdoc_save is rated Medium
This tool creates or modifies files on disk, which is a reversible write operation. It falls under the Write category rather than Destructive because saving a document does not irreversibly delete data—the original can be restored or overwritten. Severity is medium because while file writes can have operational impact, they are generally reversible and don't directly move money or execute arbitrary code.
From the tool's definition Tool description states 'Save the document to disk. Writes to the original path unless "out" is specified.' This explicitly performs a write operation that modifies or creates files on disk.
Attacks that exploit this kind of access
The rule that runs superdoc_save safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Superdoc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For superdoc_save, this is the rule to start with:
superdoc_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Superdoc, apply this rule, and every superdoc_save call is checked against it from then on.
Questions about superdoc_save
Save the document to disk. Writes to the original path unless "out" is specified. It is categorised as a Write tool in the Superdoc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
superdoc_save accepts 2 parameters: out, session_id. Required: session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Superdoc MCP server in PolicyLayer and add a rule for superdoc_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 Superdoc. Nothing to install.
superdoc_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 superdoc_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 superdoc_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.
superdoc_save is provided by the Superdoc MCP server (@superdoc/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Superdoc, and thousands of servers like it.
This server
Across the catalogue