Show the current state of the RAG index for a project directory.
AI agents call index_status to retrieve information from Local Rag without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about the RAG index state with no side effects. It is a read-only diagnostic operation that queries the index status, making it a Read category risk with low severity since misuse would only expose metadata about the indexing state, not create, modify, delete, or execute any operations.
From the tool's definition Tool name is 'index_status' and description states it 'Show[s] the current state of the RAG index for a project directory' — a pure query operation that retrieves and displays indexing metadata without modifying any data or triggering external operations.
Documented attack patterns abuse exactly the kind of access index_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Local Rag, and nothing reaches the server without passing your rules. This is the rule we recommend for index_status:
{
"version": "1",
"default": "deny",
"tools": {
"index_status": {}
}
}index_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Show the current state of the RAG index for a project directory. It is categorised as a Read tool in the Local Rag MCP Server, which means it retrieves data without modifying state.
Register the Local Rag 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 Local Rag. 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 Local Rag MCP server (thewinci/mimirs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Local Rag, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 Local Rag tools catalogued and risk-classified — across an index of 43,000+ MCP servers.