createVegaDataUploadSession
Create a PUT upload URL for a Vega/Vega-Lite data file. Use returned assetUrl in your Vega spec.
This record as markdown: /tools/io-stablebaseline-sb/createvegadatauploadsession.md
What createVegaDataUploadSession does on Stable Baseline
AI agents use createVegaDataUploadSession 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. sales-data.csv). Extension auto-detects content type. |
documentId | string | Yes | |
contentType | string | — | MIME type override. Auto-detected from extension if omitted. |
Parameters from the server's own tool schema.
Why createVegaDataUploadSession is rated Medium
This tool creates an upload session and returns a URL for writing data files (Vega/Vega-Lite visualizations). The PUT operation modifies the server's data store by adding new visualization data assets. This is a Write operation—it creates and stores new data reversibly.
From the tool's definition Create a PUT upload URL for a Vega/Vega-Lite data file. Use returned assetUrl in your Vega spec.
Risk signalsAccepts file system path (fileName)
Attacks that exploit this kind of access
The rule that runs createVegaDataUploadSession 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 createVegaDataUploadSession, this is the rule to start with:
createVegaDataUploadSession 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 createVegaDataUploadSession call is checked against it from then on.
Questions about createVegaDataUploadSession
Create a PUT upload URL for a Vega/Vega-Lite data file. Use returned assetUrl in your Vega spec. 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.
createVegaDataUploadSession accepts 3 parameters: fileName, documentId, contentType. Required: fileName, 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 createVegaDataUploadSession: 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.
createVegaDataUploadSession 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 createVegaDataUploadSession 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 createVegaDataUploadSession. 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.
createVegaDataUploadSession 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