deleteImageInDocument
Delete an image from a document and storage.
This record as markdown: /tools/io-stablebaseline-sb/deleteimageindocument.md
What deleteImageInDocument does on Stable Baseline
AI agents call deleteImageInDocument 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 |
|---|---|---|---|
imageId | string | Yes | Image ID from IMAGE_OMITTED markers. |
Parameters from the server's own tool schema.
Why deleteImageInDocument is rated Critical
This tool irreversibly removes data (an image) from multiple locations (document and storage). Once deleted, the image cannot be recovered through normal means. This meets the definition of Destructive (irreversibly deletes data). Severity is high because an agent could inadvertently delete important visual documentation, diagrams, or evidence that are part of the company knowledge base, with no undo capability.
From the tool's definition Tool name contains 'delete' and description states 'Delete an image from a document and storage' — irreversible removal of data from both the document and persistent storage.
Attacks that exploit this kind of access
The rule that runs deleteImageInDocument 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 deleteImageInDocument, this is the rule to start with:
deleteImageInDocument 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 deleteImageInDocument call is checked against it from then on.
Questions about deleteImageInDocument
Delete an image from a document and storage. 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.
deleteImageInDocument accepts 1 parameter: imageId. Required: imageId. 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 deleteImageInDocument: 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.
deleteImageInDocument 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 deleteImageInDocument 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 deleteImageInDocument. 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.
deleteImageInDocument 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