Get the results of a completed job execution. Only works when job status is COMPLETED
AI agents call get_job_results to retrieve information from Opus 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 the results of an already-completed job without modifying, executing, or deleting anything. It is a read-only operation that queries job results data. The fact that it requires the job to be in COMPLETED status shows it operates on stable, finalized data with no ability to affect job execution or state.
From the tool's definition Tool name is 'get_job_results' and description states it retrieves/gets results of a completed job execution with no mention of modification, deletion, or side effects. The function is purely retrieving data output.
Attacks that exploit this kind of access
Get the results of a completed job execution. Only works when job status is COMPLETED. It is categorised as a Read tool in the Opus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Opus MCP Server MCP server in PolicyLayer and add a rule for get_job_results: 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 Opus MCP Server. Nothing to install.
get_job_results 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_results 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_results. 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_results is provided by the Opus MCP Server MCP server (moenamatics/opus-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 →