AI agents call get_pdf_metadata 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 metadata (such as title, author, creation date, page count) from a PDF document. It performs a query operation with no ability to modify, delete, or execute code. All sibling tools on this server (read_*, search_*) are similarly read-only operations. Metadata retrieval is a classic Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'get_pdf_metadata' and description states 'Get metadata from a PDF file.' The verb 'get' and the read-only nature of metadata extraction indicate no data modification or side effects.
Documented attack patterns abuse exactly the kind of access get_pdf_metadata 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 get_pdf_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"get_pdf_metadata": {}
}
}get_pdf_metadata 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 metadata 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 get_pdf_metadata: 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.
get_pdf_metadata 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_pdf_metadata 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_pdf_metadata. 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_pdf_metadata 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.