Comprehensive PDF health and quality analysis
AI agents call analyze_pdf_health 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 performs analysis and quality assessment of PDF documents, retrieving and reporting metadata, structural integrity, and other diagnostic information. It has no side effects, does not modify the PDF, does not execute arbitrary code, and does not delete or move data. It falls clearly into the Read category—a diagnostic inspection that yields information about the document state.
From the tool's definition Tool name 'analyze_pdf_health' combined with description 'Comprehensive PDF health and quality analysis' indicates inspection and reporting on document properties, not modification or execution of external code.
Documented attack patterns abuse exactly the kind of access analyze_pdf_health 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 analyze_pdf_health:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_pdf_health": {}
}
} analyze_pdf_health 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.
Comprehensive PDF health and quality analysis. 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 analyze_pdf_health: 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.
analyze_pdf_health 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 analyze_pdf_health 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 analyze_pdf_health. 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.
analyze_pdf_health 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.