getDocumentIngestJob
Read the current status of an ingest job. Returns { status, stage, processedImages, totalImages, documentId, error?, lastHeartbeatAt }. Stages: pending → downloaded → extracted → draft_saved → images_processing → finalized → cleaned_up. Status: queued, running, succeeded, failed, cancelled. The a...
This record as markdown: /tools/io-stablebaseline-sb/getdocumentingestjob.md
What getDocumentIngestJob does on Stable Baseline
AI agents call getDocumentIngestJob 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 |
|---|---|---|---|
jobId | string | Yes |
Parameters from the server's own tool schema.
Why getDocumentIngestJob is rated Low
This tool performs a pure information retrieval operation—it queries the state of a document ingest job and returns metadata about processing progress. There are no side effects, data modifications, deletions, or external operations triggered. The tool is read-only and poses minimal security risk if misused by an agent.
From the tool's definition Tool name 'getDocumentIngestJob' and description 'Read the current status of an ingest job. Returns { status, stage, processedImages, totalImages, documentId, error?, lastHeartbeatAt }.' The description explicitly uses 'Read' and the tool only retrieves and…
Attacks that exploit this kind of access
The rule that runs getDocumentIngestJob 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 getDocumentIngestJob, this is the rule to start with:
getDocumentIngestJob 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 getDocumentIngestJob call is checked against it from then on.
Questions about getDocumentIngestJob
Read the current status of an ingest job. Returns { status, stage, processedImages, totalImages, documentId, error?, lastHeartbeatAt }. Stages: pending → downloaded → extracted → draft_saved → images_processing → finalized → cleaned_up. Status: queued, running, succeeded, failed, cancelled. The associated document_id is populated immediately and progressively filled in as images are processed. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getDocumentIngestJob accepts 1 parameter: jobId. Required: jobId. 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 getDocumentIngestJob: 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.
getDocumentIngestJob 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 getDocumentIngestJob 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 getDocumentIngestJob. 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.
getDocumentIngestJob 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