exportDocument
Export a Stable Baseline document as a PDF or an editable Word document (docx), styled with the organisation's brand, or with an export template when templateId is given. Give it the documentId (a UUID, or a friendly id such as DOC-123) and the format: 'pdf' (default) or 'docx'. The file is made ...
This record as markdown: /tools/io-stablebaseline-sb/exportdocument.md
What exportDocument does on Stable Baseline
AI agents use exportDocument to create or update resources in Stable Baseline, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stable Baseline environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
format | string | — | Output format. 'pdf' (default) = a PDF with a table of contents; 'docx' = an editable Word document. |
documentId | string | Yes | The document to export: its id, or its friendly id (for example DOC-123). A whiteboard is not a document here: use exportFromWhiteboard. |
templateId | string | — | Optional. An export template of the organisation (set up in the app's export templates) to use instead of the brand styling: its cover, document control page an |
Parameters from the server's own tool schema.
Why exportDocument is rated Medium
An AI agent can call exportDocument faster than any human can review: one bad instruction and it creates or modifies resources in Stable Baseline by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs exportDocument safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For exportDocument, this is the rule to start with:
exportDocument 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 Stable Baseline, apply this rule, and every exportDocument call is checked against it from then on.
Questions about exportDocument
Export a Stable Baseline document as a PDF or an editable Word document (docx), styled with the organisation's brand, or with an export template when templateId is given. Give it the documentId (a UUID, or a friendly id such as DOC-123) and the format: 'pdf' (default) or 'docx'. The file is made in the background: if that takes longer than one tool call can wait, this returns status 'exporting' with a jobId; wait about 30 seconds, then call this tool AGAIN with the SAME arguments to collect it. Nothing is exported twice while one export is running, so calling again is cheap and safe. When it is ready the answer carries a download link in 'url', available for 1 hour. Inside an organisation agent's job the file is kept with the job instead, and the answer carries its fileId for the next tool to use. PDF and Word export depend on the organisation's plan; when the plan does not include them, the answer says so. A whiteboard is exported with exportFromWhiteboard, not this tool. It is categorised as a Write tool in the Stable Baseline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
exportDocument accepts 3 parameters: format, documentId, templateId. Required: documentId. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for exportDocument: 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 Stable Baseline. Nothing to install.
exportDocument 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 exportDocument 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 exportDocument. 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.
exportDocument is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue