updateImageInDocument

Update image metadata (alt, caption, dimensions, alignment). Requires the document's versionTimestamp (from getDocument or any mutating tool's response) for optimistic locking.

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

Medium RISK CLASS

Category Write

Parameters 81 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What updateImageInDocument does on Stable Baseline

AI agents use updateImageInDocument 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
`alt`	string	—	New alt text.
`align`	string	—	Alignment.
`width`	number	—	Width in pixels.
`height`	number	—	Height in pixels.
`caption`	string	—	New caption.
`imageId`	string	Yes	Image ID from IMAGE_OMITTED markers.
`nlDescription`	string	—	New image description.
`documentVersionTimestamp`	number	—	Optimistic-lock token: the document's versionTimestamp from getDocument() or any mutating tool's response. (Alias accepted: versionTimestamp.)

Parameters from the server's own tool schema.

RISK

Why updateImageInDocument is rated Medium

This tool creates or modifies data (image metadata) within a document in a reversible manner. It does not delete, execute code, move money, or trigger external operations. The requirement for versionTimestamp indicates optimistic locking to prevent conflicts, a typical Write pattern.

From the tool's definition Tool name 'updateImageInDocument' and description stating it updates image metadata (alt, caption, dimensions, alignment), which are reversible modifications to document content.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs updateImageInDocument 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 updateImageInDocument, this is the rule to start with:

updateImageInDocument Rate-limited

updateImageInDocument 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": {
    "updateImageInDocument": {
      "limits": [
        {
          "counter": "updateimageindocument_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 updateImageInDocument call is checked against it from then on.

FAQ

Questions about updateImageInDocument

What does the updateImageInDocument tool do? +

Update image metadata (alt, caption, dimensions, alignment). Requires the document's versionTimestamp (from getDocument or any mutating tool's response) for optimistic locking. 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 updateImageInDocument accept? +

updateImageInDocument accepts 8 parameters: alt, align, width, height, caption, imageId, nlDescription, documentVersionTimestamp. Required: imageId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on updateImageInDocument? +

Register the Stable Baseline MCP server in PolicyLayer and add a rule for updateImageInDocument: 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 updateImageInDocument? +

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

Can I rate-limit updateImageInDocument? +

Yes. Add a rate_limit block to the updateImageInDocument 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 updateImageInDocument completely? +

Set action: deny in the PolicyLayer policy for updateImageInDocument. 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 updateImageInDocument? +

updateImageInDocument 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 196 Stable Baseline tools →

Across the catalogue

The MCP Attack Database →

Guides

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