Check the status of a submitted Sage job
AI agents call check_job_status to retrieve information from Sage MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read operation to query the current state of an existing job. It has no side effects, does not execute code or commands, and does not modify or delete data. The blast radius of misuse is minimal—an agent could only retrieve status information about jobs, which is a non-sensitive query operation in the context of a scientific computing platform.
From the tool's definition The tool name 'check_job_status' and description 'Check the status of a submitted Sage job' indicate a query-only operation that retrieves status information without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Check the status of a submitted Sage job. It is categorised as a Read tool in the Sage MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP Server MCP server in PolicyLayer and add a rule for check_job_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 Sage MCP Server. Nothing to install.
check_job_status 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 check_job_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.
Set action: deny in the PolicyLayer policy for check_job_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.
check_job_status is provided by the Sage MCP Server MCP server (waggle-sensor/sage-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 →