Returns status of an async job
AI agents call get_async_job_status to retrieve information from PDF Generator API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only retrieval of job status information. There are no side effects, data modifications, code execution, or destructive operations. Even in the context of a PDF generation service where sibling tools create documents and templates, this tool merely queries the state of existing asynchronous operations.
From the tool's definition Tool name is 'get_async_job_status' and description states it 'Returns status of an async job' — this is a pure query operation that retrieves job status information without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
Returns status of an async job. It is categorised as a Read tool in the PDF Generator API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PDF Generator API MCP Server MCP server in PolicyLayer and add a rule for get_async_job_status: 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 PDF Generator API MCP Server. Nothing to install.
get_async_job_status 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_async_job_status 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_async_job_status. 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_async_job_status is provided by the PDF Generator API MCP Server MCP server (pdfgeneratorapi/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 →