Extract metadata and basic information from a PDF file, including page count, file size, creation dates, and document properties. Use either absolute_path for any location or relative_path for files in ~/pdf-agent/ directory.
AI agents call get_pdf_metadata to retrieve information from PDF Agent MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads and returns document metadata (page count, file size, creation dates, properties) without modifying, executing, or deleting anything. This is a straightforward Read operation. Severity is low because metadata extraction poses minimal risk even if misused by an agent—it only reveals document properties, not sensitive content, and causes no state changes.
From the tool's definition Tool performs 'Extract metadata and basic information from a PDF file, including page count, file size, creation dates, and document properties' — purely retrieval operations with no 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 PDF Agent MCP, 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.
Extract metadata and basic information from a PDF file, including page count, file size, creation dates, and document properties. Use either absolute_path for any location or relative_path for files in ~/pdf-agent/ directory. It is categorised as a Read tool in the PDF Agent MCP MCP Server, which means it retrieves data without modifying state.
Register the PDF Agent 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 Agent MCP. 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 Agent MCP server (vlad-ds/pdf-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PDF Agent MCP, 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.
7 PDF Agent MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.