createDocumentFromUpload
Step 2 of file ingest. After the file is uploaded via the PUT URL from createDocumentIngestSession, call this to start the async conversion. Returns { jobId, documentId } immediately — the document is created as a draft and progressively populated as the worker processes the file. Poll getDocumen...
This record as markdown: /tools/io-stablebaseline-sb/createdocumentfromupload.md
What createDocumentFromUpload does on Stable Baseline
AI agents use createDocumentFromUpload 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 |
|---|---|---|---|
title | string | — | Optional document title. Defaults to the upload's filename without extension. |
folderId | string | — | Optional folder. Must belong to projectId. |
projectId | string | Yes | Must match the project the session was created for. |
sessionId | string | Yes | From createDocumentIngestSession. |
changeSummary | string | — | Optional changelog message for the version snapshot taken when the ingest finalises. |
Parameters from the server's own tool schema.
Why createDocumentFromUpload is rated Medium
This tool creates documents (reversible write operation). The blast radius is medium because: (1) new documents become part of the company's knowledge base, (2) if invoked carelessly on large/sensitive files, it could populate the knowledge graph with unintended content, but (3) documents are created as drafts and the operation is reversible (deletion implied by other tooling).
From the tool's definition Tool description states the tool 'start[s] the async conversion' and 'the document is created as a draft', indicating document creation with side effects. Described as 'Step 2 of file ingest', confirming it modifies system state by creating new documents.
Attacks that exploit this kind of access
The rule that runs createDocumentFromUpload 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 createDocumentFromUpload, this is the rule to start with:
createDocumentFromUpload 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 createDocumentFromUpload call is checked against it from then on.
Questions about createDocumentFromUpload
Step 2 of file ingest. After the file is uploaded via the PUT URL from createDocumentIngestSession, call this to start the async conversion. Returns { jobId, documentId } immediately — the document is created as a draft and progressively populated as the worker processes the file. Poll getDocumentIngestJob({ jobId }) to track progress. Idempotent: calling twice with the same sessionId returns the same job/document. 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.
createDocumentFromUpload accepts 5 parameters: title, folderId, projectId, sessionId, changeSummary. Required: projectId, sessionId. 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 createDocumentFromUpload: 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.
createDocumentFromUpload 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 createDocumentFromUpload 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 createDocumentFromUpload. 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.
createDocumentFromUpload 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