get_server_info

THE RISK

Low Risk

Why get_server_info needs a policy

This tool performs only information retrieval operations—it queries server state and returns capabilities information. There are no side effects, data modifications, code execution, or destructive operations. The blast radius of misuse is minimal since an AI agent obtaining server information cannot cause harm beyond learning what operations are available. This is a standard Read category operation.

From the tool's definition The tool name 'get_server_info' and description 'Get comprehensive server information and available capabilities' indicate it retrieves and queries server metadata without modifying anything. The verb 'Get' is explicitly retrieval-focused.

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

POLICY

How to control get_server_info

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

policy.json

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

get_server_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 MCP PDF — 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 MCP PDF tools

Write optimize_pdf Optimize PDF file size and performance Write reorder_pdf_pages Reorder pages in a PDF document Write repair_pdf Attempt to repair corrupted or damaged PDF files Write rotate_pages Rotate specific pages by 90, 180, or 270 degrees Write split_pdf Split PDF into multiple files at specified pages Write split_pdf_by_bookmarks Split PDF into separate files using bookmarks as breakpoints Write split_pdf_by_pages Split PDF into separate files by page ranges Write add_date_field Add a date field with format validation to PDF

All 46 MCP PDF 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_server_info

What does the get_server_info tool do? +

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

How do I enforce a policy on get_server_info? +

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

What risk level is get_server_info? +

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

Can I rate-limit get_server_info? +

Yes. Add a rate_limit block to the get_server_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_server_info completely? +

Set action: deny in the PolicyLayer policy for get_server_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_server_info? +

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

Enforce policy on every MCP PDF tool call.

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

CHECK YOUR STACK →