Checks the status of a previously submitted ingestion job.
AI agents call getIngestJobRunStatus to retrieve information from SourceSync Ai MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about an existing ingestion job. It performs a query operation with no side effects—it does not create, modify, delete, or execute anything. The action is informational only, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'getIngestJobRunStatus' and description 'Checks the status of a previously submitted ingestion job' indicate a read-only operation that queries job status without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Checks the status of a previously submitted ingestion job. It is categorised as a Read tool in the SourceSync Ai MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SourceSync Ai MCP Server MCP server in PolicyLayer and add a rule for getIngestJobRunStatus: 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 SourceSync Ai MCP Server. Nothing to install.
getIngestJobRunStatus 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 getIngestJobRunStatus 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 getIngestJobRunStatus. 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.
getIngestJobRunStatus is provided by the SourceSync Ai MCP Server MCP server (sitegpt/sourcesyncai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →