createVegaDataUploadSession

Create a PUT upload URL for a Vega/Vega-Lite data file. Use returned assetUrl in your Vega spec.

SERVERStable Baseline SOURCEhttps://api.stablebaseline.io/functions/v1/cloud-serve/mcp

Medium RISK CLASS

Category Write

Parameters 42 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-stablebaseline-sb/createvegadatauploadsession.md

WHAT IT DOES

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.
`projectId`	string	—	Optional. Narrows a friendly-id lookup to one project. Only needed when a friendly id is ambiguous — TAS-/IMP-/PLN- ids are numbered per PROJECT, so the same id
`documentId`	string	Yes
`contentType`	string	—	MIME type override. Auto-detected from extension if omitted.

Parameters from the server's own tool schema.

RISK

Why createVegaDataUploadSession is rated Medium

This tool creates a new upload session and asset, which is a write operation that modifies the workspace by adding visualization data. The severity is medium because uploaded data could affect reports/dashboards used for decision-making, but the blast radius is limited to data visualization assets rather than core company data or financial systems.

From the tool's definition 'Create a PUT upload URL for a Vega/Vega-Lite data file' indicates file creation/upload that modifies the system state by adding new data assets that can be referenced in visualizations.

Risk signalsAccepts file system path (fileName)

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "createVegaDataUploadSession": {
      "limits": [
        {
          "counter": "createvegadatauploadsession_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about createVegaDataUploadSession

What does the createVegaDataUploadSession tool do? +

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.

What parameters does createVegaDataUploadSession accept? +

createVegaDataUploadSession accepts 4 parameters: fileName, projectId, documentId, contentType. Required: fileName, documentId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on createVegaDataUploadSession? +

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.

What risk level is createVegaDataUploadSession? +

createVegaDataUploadSession is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit createVegaDataUploadSession? +

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.

How do I block createVegaDataUploadSession completely? +

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.

What MCP server provides createVegaDataUploadSession? +

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.

KEEP EXPLORING

More on Stable Baseline, and thousands of servers like it.

This server

All 222 Stable Baseline tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →