This record as markdown: /tools/0xpdf-mcp/list-schemas.md
What list_schemas does on 0xpdf
AI agents call list_schemas to retrieve information from 0xpdf without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_schemas is rated Low
This tool queries and retrieves schema metadata from an API endpoint without creating, modifying, deleting, or executing any operations. It is a simple data retrieval endpoint with minimal blast radius if misused by an AI agent—worst case, an agent could enumerate available schemas, which poses only an informational disclosure risk.
From the tool's definition Tool name 'list_schemas' and description 'List user schemas from /api/v1/schemas' indicate a retrieval operation with no side effects. The verb 'list' is a classic read-only operation.
Attacks that exploit this kind of access
The rule that runs list_schemas safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0xpdf, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_schemas, this is the rule to start with:
list_schemas is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 0xpdf, apply this rule, and every list_schemas call is checked against it from then on.
Questions about list_schemas
List user schemas from /api/v1/schemas. It is categorised as a Read tool in the 0xpdf MCP Server, which means it retrieves data without modifying state.
Register the 0xpdf MCP server in PolicyLayer and add a rule for list_schemas: 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 0xpdf. Nothing to install.
list_schemas 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_schemas 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_schemas. 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_schemas is provided by the 0xpdf MCP server (risha-max/0xpdf-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0xpdf, and thousands of servers like it.
This server
Across the catalogue