Get the results of a previously submitted job
AI agents call get_job_results to retrieve information from Quack MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves results from an already-executed job. It performs data retrieval without modifying, executing, or deleting anything. The action is purely informational—fetching output from a prior operation. No code execution, resource deletion, or external state changes occur. This is a straightforward read operation with minimal risk if misused by an agent.
From the tool's definition Tool name 'get_job_results' and description 'Get the results of a previously submitted job' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the results of a previously submitted job. It is categorised as a Read tool in the Quack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Quack 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 Quack 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 Quack MCP Server MCP server (smhajimirzaei/quack-mcp-server). 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 →