pdf-metadata
A read tool on the MCP PDF Reader MCP server.
This record as markdown: /tools/3351163616-mcp-pdf-reader/pdf-metadata.md
What pdf-metadata does on MCP PDF Reader
AI agents call pdf-metadata to retrieve information from MCP PDF Reader without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pdf-metadata is rated Low
Metadata retrieval from PDFs is a read-only operation with no side effects. It queries document properties without modifying, executing, or deleting anything. The empty description lowers confidence slightly, but the naming convention and server context strongly indicate this is a straightforward metadata extraction tool. Severity is low because metadata exposure poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'pdf-metadata' combined with server description stating it 'retrieves metadata through the Model Context Protocol'. The sibling tools (ocr-pdf-auto-legacy, read-pdf, search-pdf, etc.) are all read operations.
Attacks that exploit this kind of access
The rule that runs pdf-metadata safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP PDF Reader, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pdf-metadata, this is the rule to start with:
pdf-metadata is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP PDF Reader, apply this rule, and every pdf-metadata call is checked against it from then on.
Questions about pdf-metadata
pdf-metadata is a read tool on the MCP PDF Reader MCP server. It is categorised as a Read tool in the MCP PDF Reader MCP Server, which means it retrieves data without modifying state.
Register the MCP PDF Reader MCP server in PolicyLayer and add a rule for 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 PDF Reader. Nothing to install.
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 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 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.
pdf-metadata is provided by the MCP PDF Reader MCP server (3351163616/mcp_pdf_reader). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP PDF Reader, and thousands of servers like it.
This server
Across the catalogue