インデックスの詳細な状態を確認します。文書数、セクション数、Dirty数、ワーカー状態が返されます。
AI agents call index_status to retrieve information from Search Docs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries index metadata without side effects. It returns status information (document count, section count, dirty count, worker state) for inspection purposes only. This is a read-only diagnostic operation with no capability to modify, delete, or execute external operations.
From the tool's definition Tool name 'index_status' and description indicate it 'checks detailed status of the index' returning counts of documents, sections, and worker state. No parameters are mentioned that could modify data or trigger operations.
Attacks that exploit this kind of access
インデックスの詳細な状態を確認します。文書数、セクション数、Dirty数、ワーカー状態が返されます。. It is categorised as a Read tool in the Search Docs MCP Server, which means it retrieves data without modifying state.
Register the Search Docs 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 Search Docs. 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 Search Docs MCP server (otolab/search-docs). 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 →