createDocumentIngestSession
Step 1 of file ingest. Mint a single-use PUT upload URL for a large file (PDF, DOCX, plain text, or markdown — up to 150 MB). Returns { sessionId, uploadUrl, expiresAt, maxBytes }. Upload the raw bytes to uploadUrl with PUT, then call createDocumentFromUpload({ sessionId, projectId }) to start th...
This record as markdown: /tools/io-stablebaseline-sb/createdocumentingestsession.md
What createDocumentIngestSession does on Stable Baseline
AI agents use createDocumentIngestSession 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 |
|---|---|---|---|
fileName | string | Yes | Original filename, e.g. report.pdf. |
folderId | string | — | Optional folder to drop the document into. Must belong to projectId. |
mimeType | string | Yes | One of: application/pdf, application/vnd.openxmlformats-officedocument.wordprocessingml.document (DOCX), text/plain, text/markdown. |
projectId | string | Yes | Target project for the resulting document. |
sizeBytes | number | — | Optional file size hint in bytes. Rejected up-front if it exceeds 150 MB. |
Parameters from the server's own tool schema.
Why createDocumentIngestSession is rated Medium
This tool initiates document creation by setting up an upload session. While it doesn't directly delete data (would be Destructive) or execute arbitrary code (would be Execute), it does create persistent records in the system.
From the tool's definition Tool creates a new ingest session and facilitates file upload. Description explicitly states 'Mint a single-use PUT upload URL' and 'start the conversion' to create a document, which are write operations that modify the system state by adding new documents.
Risk signalsAccepts file system path (fileName)
Attacks that exploit this kind of access
The rule that runs createDocumentIngestSession 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 createDocumentIngestSession, this is the rule to start with:
createDocumentIngestSession 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 createDocumentIngestSession call is checked against it from then on.
Questions about createDocumentIngestSession
Step 1 of file ingest. Mint a single-use PUT upload URL for a large file (PDF, DOCX, plain text, or markdown — up to 150 MB). Returns { sessionId, uploadUrl, expiresAt, maxBytes }. Upload the raw bytes to uploadUrl with PUT, then call createDocumentFromUpload({ sessionId, projectId }) to start the conversion. The file is auto-deleted once the document is created. 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.
createDocumentIngestSession accepts 5 parameters: fileName, folderId, mimeType, projectId, sizeBytes. Required: fileName, mimeType, projectId. 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 createDocumentIngestSession: 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.
createDocumentIngestSession 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 createDocumentIngestSession 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 createDocumentIngestSession. 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.
createDocumentIngestSession 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