Get information about the current documentation index, including
AI agents call get_index_info to retrieve information from Whoosh RAG MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries metadata about an existing documentation index. It retrieves status information without creating, modifying, executing, deleting, or moving resources. The 'Get information' verb and read-only nature of index metadata inspection places it squarely in the Read category with low severity—misuse would only expose documentation structure details, not cause harm.
From the tool's definition Tool name 'get_index_info' and description 'Get information about the current documentation index' indicate a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
Get information about the current documentation index, including. It is categorised as a Read tool in the Whoosh RAG MCP MCP Server, which means it retrieves data without modifying state.
Register the Whoosh RAG MCP server in PolicyLayer and add a rule for get_index_info: 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 Whoosh RAG MCP. Nothing to install.
get_index_info 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_index_info 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_index_info. 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_index_info is provided by the Whoosh RAG MCP server (jianlins/whoosh_rag_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 →