Get comprehensive server information
AI agents call server_info to retrieve information from MCP PDF without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns server information—a read-only operation with no side effects. It does not create, modify, delete, execute code, or trigger external operations. The primary risk is information disclosure about server capabilities, which is typically low severity since server information is often already known to legitimate users and the blast radius of misuse is minimal.
From the tool's definition Tool name 'server_info' and description 'Get comprehensive server information' indicate a retrieval operation that queries server metadata without modification or execution of external operations.
Documented attack patterns abuse exactly the kind of access server_info gives an agent:
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 server_info:
{
"version": "1",
"default": "deny",
"tools": {
"server_info": {}
}
} server_info 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.
Get comprehensive server information. It is categorised as a Read tool in the MCP PDF MCP Server, which means it retrieves data without modifying state.
Register the MCP PDF MCP server in PolicyLayer and add a rule for 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.
server_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 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.
Set action: deny in the PolicyLayer policy for 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.
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.
Start from MCP PDF, 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.
46 MCP PDF tools catalogued and risk-classified — across an index of 43,000+ MCP servers.