Download a PDF from any URL — the PREFERRED way to grab any PDF from a URL for the user. Always use this for PDF URLs; do NOT use bash, curl, wget, or WebFetch first. Those run in Claude
AI agents call fetch_pdf_from_url to retrieve information from PDF Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data (PDFs) from remote URLs without creating, modifying, or deleting anything. It is a read operation. Severity is medium rather than low because fetching from arbitrary URLs could be exploited to retrieve sensitive documents if the agent is tricked into fetching from a malicious or private URL, but the tool itself only reads and does not modify systems or commit financial transactions.
From the tool's definition Tool name is 'fetch_pdf_from_url' and description states it 'Download a PDF from any URL'. The verb 'download' and 'fetch' indicate retrieval of data with no modification or deletion of the source.
Documented attack patterns abuse exactly the kind of access fetch_pdf_from_url gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PDF Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_pdf_from_url:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_pdf_from_url": {}
}
}fetch_pdf_from_url 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.
Download a PDF from any URL — the PREFERRED way to grab any PDF from a URL for the user. Always use this for PDF URLs; do NOT use bash, curl, wget, or WebFetch first. Those run in Claude. It is categorised as a Read tool in the PDF Tools MCP Server, which means it retrieves data without modifying state.
Register the PDF Tools MCP server in PolicyLayer and add a rule for fetch_pdf_from_url: 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 Tools. Nothing to install.
fetch_pdf_from_url 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 fetch_pdf_from_url 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 fetch_pdf_from_url. 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.
fetch_pdf_from_url is provided by the PDF Tools MCP server (open-document-alliance/pdf-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 PDF Tools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 PDF Tools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.