get_document_structure
AI agents call get_document_structure to retrieve information from PDF Indexer MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves structural information about an indexed PDF document—likely returning sections, chapters, or organizational hierarchy. This is a query operation with no side effects, modifications, or destructive capabilities. The low severity reflects minimal blast radius: misuse would only surface unwanted structural metadata, not compromise data integrity or trigger external operations.
From the tool's definition Tool name 'get_document_structure' indicates retrieval of metadata about a PDF's structure. The sibling tools (download_pdf, index_pdf, chunk_pdf, search_research_papers) establish this as a document analysis server with no capability to modify or delete data.
Attacks that exploit this kind of access
get_document_structure. It is categorised as a Read tool in the PDF Indexer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PDF Indexer MCP Server MCP server in PolicyLayer and add a rule for get_document_structure: 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 Indexer MCP Server. Nothing to install.
get_document_structure 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 get_document_structure 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 get_document_structure. 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.
get_document_structure is provided by the PDF Indexer MCP Server MCP server (lizthedeveloper/pdf-indexer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →