ingest_status

Check progress of a running or completed ingestion job.

Server Resolve jenkinsm13/resolve-mcp
Category Read
Risk class Low
Parameters 00 required

What ingest_status does on Resolve

AI agents call ingest_status to retrieve information from Resolve without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why ingest_status needs a policy

This tool retrieves information about an ongoing or past ingestion process. It performs a read-only check of progress metrics and status, with no side effects, data modification, or execution capability. The blast radius of misuse is minimal—an agent could only waste time checking status repeatedly or leak ingestion progress information.

From the tool's definition Tool name 'ingest_status' and description 'Check progress of a running or completed ingestion job' indicate a query operation that retrieves status information without modifying state or triggering new operations.

Questions about ingest_status

What does the ingest_status tool do? +

Check progress of a running or completed ingestion job. It is categorised as a Read tool in the Resolve MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ingest_status? +

Register the Resolve MCP server in PolicyLayer and add a rule for ingest_status: 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 Resolve. Nothing to install.

What risk level is ingest_status? +

ingest_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ingest_status? +

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

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

ingest_status is provided by the Resolve MCP server (jenkinsm13/resolve-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.