Get the results of a completed job.
AI agents call get_job_result to retrieve information from ESMfold 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 output from a previously executed job. It performs no modification, deletion, or execution of code—only fetches and returns data. The operation is passive and non-destructive, consistent with Read category classification. Low severity because retrieval of analysis results poses minimal risk; any misuse would only expose data that was already computed and stored.
From the tool's definition Tool name 'get_job_result' with description 'Get the results of a completed job' indicates data retrieval with no side effects. The verb 'Get' and action of retrieving completed results are characteristic of Read operations.
Attacks that exploit this kind of access
Get the results of a completed job. It is categorised as a Read tool in the ESMfold MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ESMfold MCP Server 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 ESMfold MCP Server. 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 ESMfold MCP Server MCP server (macromnex/esmfold_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 →