Get the results of a completed job.
AI agents call get_job_result to retrieve information from SPIRED-Stab MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves previously computed results from a completed job. It does not modify, delete, execute code, or commit any resources. The operation is a simple query/fetch of existing data, which falls squarely under the Read category. Severity is low because misuse (e.g., an agent repeatedly fetching results) poses minimal risk compared to other tool categories.
From the tool's definition Tool name is 'get_job_result' and description states it 'Get the results of a completed job' — this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the results of a completed job. It is categorised as a Read tool in the SPIRED-Stab MCP MCP Server, which means it retrieves data without modifying state.
Register the SPIRED-Stab MCP server in PolicyLayer and add a rule for get_job_result: 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 SPIRED-Stab MCP. Nothing to install.
get_job_result 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 get_job_result 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 get_job_result. 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.
get_job_result is provided by the SPIRED-Stab MCP server (macromnex/spired_stab_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 →