getImageInDocument
Get image details including a fresh signed URL (expires after 1 hour). Use storagePath from IMAGE_OMITTED markers in getDocument output.
This record as markdown: /tools/io-stablebaseline-sb/getimageindocument.md
What getImageInDocument does on Stable Baseline
AI agents call getImageInDocument to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
documentId | string | Yes | |
storagePath | string | Yes | Storage path from IMAGE_OMITTED marker. |
Parameters from the server's own tool schema.
Why getImageInDocument is rated Low
This tool retrieves image metadata and generates temporary signed URLs for authorized access to existing documents. It has no side effects—it queries data without modifying, deleting, or executing anything. The 1-hour expiration of the signed URL is a standard access control mechanism, not a risk amplifier.
From the tool's definition Tool description states 'Get image details including a fresh signed URL' – a retrieval operation. Specifically 'Get' (read) with no modification, deletion, or execution component.
Attacks that exploit this kind of access
The rule that runs getImageInDocument 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 getImageInDocument, this is the rule to start with:
getImageInDocument is read-only, so it stays allowed. 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 getImageInDocument call is checked against it from then on.
Questions about getImageInDocument
Get image details including a fresh signed URL (expires after 1 hour). Use storagePath from IMAGE_OMITTED markers in getDocument output. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getImageInDocument accepts 2 parameters: documentId, storagePath. Required: documentId, storagePath. 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 getImageInDocument: 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.
getImageInDocument is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getImageInDocument 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 getImageInDocument. 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.
getImageInDocument 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