superdoc_close
Close a document session and release memory. Unsaved changes will be lost.
This record as markdown: /tools/superdoc-mcp/superdoc-close.md
What superdoc_close does on Superdoc
AI agents use superdoc_close 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 |
|---|---|---|---|
session_id | string | Yes | Session ID to close. |
Parameters from the server's own tool schema.
Why superdoc_close is rated Medium
While closing a session could be considered a destructive action in some contexts, the evidence that unsaved changes are explicitly discarded suggests this is a controlled session-termination operation rather than data deletion. The user can reopen the document afterward. However, it crosses into Write territory because it modifies the application state (session status) irreversibly within the current workflow.
From the tool's definition Tool name 'superdoc_close' combined with description stating 'Unsaved changes will be lost' indicates it closes/terminates a document session.
Attacks that exploit this kind of access
The rule that runs superdoc_close 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_close, this is the rule to start with:
superdoc_close 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_close call is checked against it from then on.
Questions about superdoc_close
Close a document session and release memory. Unsaved changes will be lost. 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_close accepts 1 parameter: 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_close: 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_close 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_close 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_close. 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_close 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