Get the total number of pages in a PDF document. This is a lightweight operation that only reads the PDF header, not the full content. Args: - file_path (string): Absolute path to a local PDF file Returns: Page count as a number. Examples: - Quick check before deciding which pages to extract - Va...
AI agents call get_page_count to retrieve information from Pdf Reader without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata (page count) from a PDF file without any side effects. It performs a read-only operation on the file system and PDF structure. The lightweight nature (header-only read) and the use cases (quick check, validation) confirm it is purely informational. No data is written, deleted, or executed.
From the tool's definition Tool description explicitly states 'Get the total number of pages in a PDF document' and 'only reads the PDF header, not the full content.' The return value is 'Page count as a number.' This is a straightforward query operation with no modification, deletion,…
Attacks that exploit this kind of access
Get the total number of pages in a PDF document. This is a lightweight operation that only reads the PDF header, not the full content. Args: - file_path (string): Absolute path to a local PDF file Returns: Page count as a number. Examples: - Quick check before deciding which pages to extract - Validate a PDF file is readable. It is categorised as a Read tool in the Pdf Reader MCP Server, which means it retrieves data without modifying state.
Register the Pdf Reader MCP server in PolicyLayer and add a rule for get_page_count: 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 Reader. Nothing to install.
get_page_count 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_page_count 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_page_count. 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_page_count is provided by the Pdf Reader MCP server (shuji-bonji/pdf-reader-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 →