AI agents call grimoire_index_status to retrieve information from Grimoire without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and reports status information about the Grimoire index. It queries existing index metadata (document count, embedding coverage, data sources, update times) without creating, modifying, executing, or deleting any data. This is a pure information retrieval operation with no side effects, placing it squarely in the Read category with low severity.
From the tool's definition Tool name 'grimoire_index_status' and description 'Show Grimoire index statistics: document count, embedding coverage, data sources, last update times' indicate retrieval of metadata about the index state with no modification or execution capability.
Attacks that exploit this kind of access
Show Grimoire index statistics: document count, embedding coverage, data sources, last update times. It is categorised as a Read tool in the Grimoire MCP Server, which means it retrieves data without modifying state.
Register the Grimoire MCP server in PolicyLayer and add a rule for grimoire_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 Grimoire. Nothing to install.
grimoire_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 grimoire_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 grimoire_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.
grimoire_index_status is provided by the Grimoire MCP server (tannernicol/grimoire). 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 →