get_pdf_index_stats
AI agents call get_pdf_index_stats to retrieve information from Metis Public Health without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries existing statistical information about the PDF index without modifying, executing, or deleting anything. It fits the 'Read' category as a data retrieval operation with no side effects. The low blast radius (only returns stats) and local-first architecture further support low severity.
From the tool's definition Tool name 'get_pdf_index_stats' indicates retrieval of statistical metadata about indexed PDFs. The name structure (get_* pattern) and context within a research companion that maintains a local PDF library strongly suggest a query operation.
Attacks that exploit this kind of access
get_pdf_index_stats. It is categorised as a Read tool in the Metis Public Health MCP Server, which means it retrieves data without modifying state.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for get_pdf_index_stats: 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 Metis Public Health. Nothing to install.
get_pdf_index_stats 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_pdf_index_stats 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_pdf_index_stats. 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_pdf_index_stats is provided by the Metis Public Health MCP server (sveritg/metis_ph). 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 →