List all available tools organized by functional category
AI agents call list_tools_by_category 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 presents metadata about available tools. It performs no data extraction from PDFs, modification of documents, code execution, or destructive operations. It is a simple enumeration/listing operation, making it a Read category tool with low severity since misuse would only expose tool availability information rather than sensitive document content or enable dangerous actions.
From the tool's definition Tool name is 'list_tools_by_category' and description states it 'List all available tools organized by functional category' — a purely informational query with no side effects.
Documented attack patterns abuse exactly the kind of access list_tools_by_category 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 list_tools_by_category:
{
"version": "1",
"default": "deny",
"tools": {
"list_tools_by_category": {}
}
} list_tools_by_category 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.
List all available tools organized by functional category. 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 list_tools_by_category: 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.
list_tools_by_category 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 list_tools_by_category 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 list_tools_by_category. 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.
list_tools_by_category 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.