Get information about a PDF file (number of pages, metadata, etc.).
AI agents call get_pdf_info to retrieve information from MD-PDF MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only operations on PDF files: querying page counts and extracting metadata. It has no side effects, cannot modify or delete data, and does not execute code or trigger external operations. It is clearly a Read category tool with low severity since metadata extraction poses minimal risk of misuse by an AI agent.
From the tool's definition Tool description states it 'Get[s] information about a PDF file (number of pages, metadata, etc.)' — purely retrieval of metadata with no modification, creation, execution, or deletion of data.
Attacks that exploit this kind of access
Get information about a PDF file (number of pages, metadata, etc.). It is categorised as a Read tool in the MD-PDF MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MD-PDF MCP Server MCP server in PolicyLayer and add a rule for get_pdf_info: 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 MD-PDF MCP Server. Nothing to install.
get_pdf_info 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_info 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_info. 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_info is provided by the MD-PDF MCP Server MCP server (kareemaly/md-pdf-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 →