createImageUploadSession
Create a PUT upload URL for a document image (max 10MB). Use the returned assetUrl with insertImageInDocument.
This record as markdown: /tools/io-stablebaseline-sb/createimageuploadsession.md
What createImageUploadSession does on Stable Baseline
AI agents use createImageUploadSession 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 |
|---|---|---|---|
sha256 | string | — | Optional SHA-256 hex digest. |
fileName | string | Yes | Original filename (e.g. screenshot.png). |
mimeType | string | Yes | Image MIME type (e.g. image/png). |
documentId | string | Yes |
Parameters from the server's own tool schema.
Why createImageUploadSession is rated Medium
This tool creates (Write) a new resource (an upload session and ultimately a stored image asset) that modifies the document management system. It is reversible via deletion, so not Destructive. The blast radius is medium because an agent could upload malicious, private, or misleading images into company knowledge base documents, but damage is limited to image data and can be deleted.
From the tool's definition Tool description states 'Create a PUT upload URL for a document image' — explicitly creating an upload session and preparing to store an image asset. The 'max 10MB' constraint indicates a real storage operation with side effects.
Risk signalsAccepts file system path (fileName)
Attacks that exploit this kind of access
The rule that runs createImageUploadSession 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 createImageUploadSession, this is the rule to start with:
createImageUploadSession 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 createImageUploadSession call is checked against it from then on.
Questions about createImageUploadSession
Create a PUT upload URL for a document image (max 10MB). Use the returned assetUrl with insertImageInDocument. 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.
createImageUploadSession accepts 4 parameters: sha256, fileName, mimeType, documentId. Required: fileName, mimeType, 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 createImageUploadSession: 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.
createImageUploadSession 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 createImageUploadSession 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 createImageUploadSession. 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.
createImageUploadSession 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