get_job_results
AI agents call get_job_results to retrieve information from Aerobic Design MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' verb pattern and context within a design automation server (where job results would be computational outputs from design calculations) indicate this retrieves data without modification or side effects. No deletion, execution of new operations, or financial impact is implied. Classified as Read with low severity due to the informational nature of accessing cached design computation results.
From the tool's definition Tool name 'get_job_results' with 'get_' prefix indicates retrieval of previously computed results. Sibling tools like 'get_current_design_state' and 'get_job_status' on this server follow the same read-only pattern.
Attacks that exploit this kind of access
get_job_results. It is categorised as a Read tool in the Aerobic Design MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Aerobic Design 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 Aerobic Design 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 Aerobic Design MCP Server MCP server (puran-water/aerobic-design-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 →