get_file_info

THE RISK

Low Risk

Why get_file_info needs a policy

This tool retrieves file information or metadata with no side effects, making it a Read operation. The minimal blast radius (information disclosure of file metadata) justifies low severity.

From the tool's definition Tool name 'get_file_info' and description 'Get file information' indicate retrieval of metadata without modification. Sibling tool 'get_pdf_info' and context of PDF manipulation server confirm this is a query-only operation.

Documented attack patterns abuse exactly the kind of access get_file_info gives an agent:

POLICY

How to control get_file_info

PolicyLayer is an MCP gateway — it sits between your AI agents and PDF MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_file_info:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_file_info": {}
  }
}

get_file_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register PDF MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More PDF MCP Server tools

Execute open_pdf_preview Open PDF file for preview. Write decrypt_pdf Decrypt password-protected PDF using PDFtk. Write encrypt_pdf encrypt_pdf Write encrypt_pdf_basic encrypt_pdf_basic Write extract_pages Extract specific pages from PDF. Write optimize_pdf Optimize PDF for web viewing using QPDF. Write repair_pdf Repair damaged PDF file using QPDF. Write rotate_pages rotate_pages

All 22 PDF MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_file_info

What does the get_file_info tool do? +

Get file information. It is categorised as a Read tool in the PDF MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_file_info? +

Register the PDF MCP Server MCP server in PolicyLayer and add a rule for get_file_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 PDF MCP Server. Nothing to install.

What risk level is get_file_info? +

get_file_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_file_info? +

Yes. Add a rate_limit block to the get_file_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.

How do I block get_file_info completely? +

Set action: deny in the PolicyLayer policy for get_file_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.

What MCP server provides get_file_info? +

get_file_info is provided by the PDF MCP Server MCP server (sohaib-2/pdf-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PDF MCP Server tool call.

Start from PDF MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →