AI agents call get_job_check to retrieve information from PDF Co MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the naming pattern and the context of a PDF processing server where jobs are commonly submitted asynchronously, 'get_job_check' most likely retrieves the status or results of a previously initiated PDF processing task. This is a read operation with no destructive or executable side effects.
From the tool's definition Tool name 'get_job_check' suggests a status or result retrieval operation typical of asynchronous job processing systems. The naming convention (get_*) indicates a read-only query operation. No description provided to confirm exact behavior.
Documented attack patterns abuse exactly the kind of access get_job_check gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PDF Co MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_job_check:
{
"version": "1",
"default": "deny",
"tools": {
"get_job_check": {}
}
}get_job_check is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_job_check. It is categorised as a Read tool in the PDF Co MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PDF Co MCP Server MCP server in PolicyLayer and add a rule for get_job_check: 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 Co MCP Server. Nothing to install.
get_job_check 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_check 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_check. 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_check is provided by the PDF Co MCP Server MCP server (pdfdotco/pdfco-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PDF Co MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
38 PDF Co MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.