Read PDF metadata including standard fields and optionally XMP metadata.
AI agents call get_pdf_metadata to retrieve information from PDF Reader MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries PDF metadata fields (standard and XMP) without creating, modifying, deleting, or executing anything. It is a pure data retrieval operation with no side effects, matching the Read category definition. Severity is low because metadata reading has minimal security impact unless the PDF contains sensitive information, but the tool itself does not amplify risk.
From the tool's definition Tool description states 'Read PDF metadata including standard fields and optionally XMP metadata' — the verb 'Read' and absence of any modification language clearly indicate retrieval without side effects.
Attacks that exploit this kind of access
Read PDF metadata including standard fields and optionally XMP metadata. It is categorised as a Read tool in the PDF Reader MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PDF Reader MCP Server 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 PDF Reader MCP Server. 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 PDF Reader MCP Server MCP server (lihongwen/pdfreadermcp). 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 →