deleteVegaDataFile
Delete a data file attachment from a document.
This record as markdown: /tools/io-stablebaseline-sb/deletevegadatafile.md
What deleteVegaDataFile does on Stable Baseline
AI agents call deleteVegaDataFile to permanently remove resources in Stable Baseline, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
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 | |
attachmentId | string | Yes | Attachment ID to delete. |
Parameters from the server's own tool schema.
Why deleteVegaDataFile is rated Critical
This tool permanently removes data (a file attachment) from a document with no apparent undo or recovery mechanism. Destructive operations that erase data carry higher severity than reversible writes, as an agent misusing this could cause loss of important company documents or knowledge artifacts referenced in the 'company brain' context.
From the tool's definition Tool name contains 'delete' and description states 'Delete a data file attachment from a document.' The verb 'delete' combined with the action of removing a file attachment indicates irreversible data removal.
Attacks that exploit this kind of access
The rule that runs deleteVegaDataFile 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 deleteVegaDataFile, this is the rule to start with:
deleteVegaDataFile is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every deleteVegaDataFile call is checked against it from then on.
Questions about deleteVegaDataFile
Delete a data file attachment from a document. It is categorised as a Destructive tool in the Stable Baseline MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
deleteVegaDataFile accepts 3 parameters: projectId, documentId, attachmentId. Required: documentId, attachmentId. 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 deleteVegaDataFile: 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.
deleteVegaDataFile is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteVegaDataFile 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 deleteVegaDataFile. 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.
deleteVegaDataFile 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.
Across the catalogue