Count PDF files in specified or default directory.
AI agents call count_pdfs_in_directory to retrieve information from 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 a simple directory scan and count, returning metadata about the number of PDF files present. It has no side effects, does not modify files, and does not execute arbitrary code. It is a read-only information retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name and description indicate it 'Count PDF files in specified or default directory' — a query operation that retrieves information without modifying, deleting, or executing code.
Documented attack patterns abuse exactly the kind of access count_pdfs_in_directory gives an agent:
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 count_pdfs_in_directory:
{
"version": "1",
"default": "deny",
"tools": {
"count_pdfs_in_directory": {}
}
} count_pdfs_in_directory 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.
Count PDF files in specified or default directory. It is categorised as a Read tool in the PDF MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PDF MCP Server MCP server in PolicyLayer and add a rule for count_pdfs_in_directory: 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.
count_pdfs_in_directory 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 count_pdfs_in_directory 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 count_pdfs_in_directory. 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.
count_pdfs_in_directory 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.
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.
Free to start. No card required.
22 PDF MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.