AI agents call read_pdf_pages to retrieve information from MCP Document Reader without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves content from PDF documents without altering, deleting, or executing anything. It has no side effects beyond fetching data. The scope is limited to reading specific pages, making it a straightforward Read category tool with low severity—misuse would only expose document contents, not compromise system integrity or enable destructive actions.
From the tool's definition Tool name 'read_pdf_pages' and description 'Read specific pages from a PDF file' indicate data retrieval with no modification. The verb 'Read' and the absence of any write, delete, or execution keywords confirm this is a retrieval operation.
Documented attack patterns abuse exactly the kind of access read_pdf_pages gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Document Reader, and nothing reaches the server without passing your rules. This is the rule we recommend for read_pdf_pages:
{
"version": "1",
"default": "deny",
"tools": {
"read_pdf_pages": {}
}
}read_pdf_pages 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.
Read specific pages from a PDF file. It is categorised as a Read tool in the MCP Document Reader MCP Server, which means it retrieves data without modifying state.
Register the MCP Document Reader MCP server in PolicyLayer and add a rule for read_pdf_pages: 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 MCP Document Reader. Nothing to install.
read_pdf_pages 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 read_pdf_pages 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 read_pdf_pages. 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.
read_pdf_pages is provided by the MCP Document Reader MCP server (jbchouinard/mcp-document-reader). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Document Reader, 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.
8 MCP Document Reader tools catalogued and risk-classified — across an index of 43,000+ MCP servers.