AI agents call index_status to retrieve information from ZotSeek without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns status information about the ZotSeek index (counts of papers and chunks). It has no side effects, does not execute external operations, and does not create, modify, or delete data. It is a straightforward Read operation with minimal risk.
From the tool's definition Tool name 'index_status' and description 'Report ZotSeek index status: number of indexed papers, total chunks' indicate a retrieval operation that reports metadata statistics about the search index without modifying, executing, or deleting data.
Attacks that exploit this kind of access
Report ZotSeek index status: number of indexed papers, total chunks,. It is categorised as a Read tool in the ZotSeek MCP Server, which means it retrieves data without modifying state.
Register the ZotSeek MCP server in PolicyLayer and add a rule for index_status: 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 ZotSeek. Nothing to install.
index_status 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 index_status 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 index_status. 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.
index_status is provided by the ZotSeek MCP server (introfini/ZotSeek). 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 →