Get the current indexing status of a codebase. Shows progress percentage for actively indexing codebases and completion status for indexed codebases.
AI agents call get_indexing_status to retrieve information from Claude Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about the indexing state of a codebase (progress percentage or completion status). It is a pure information query with no capability to modify, delete, or execute operations. The low severity reflects that misuse would only expose internal status information, not cause harm to data or systems.
From the tool's definition Tool name 'get_indexing_status' and description 'Get the current indexing status' indicate a query operation that retrieves status information without modifying data. No side effects, mutations, or external operations are performed.
Documented attack patterns abuse exactly the kind of access get_indexing_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Context, and nothing reaches the server without passing your rules. This is the rule we recommend for get_indexing_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_indexing_status": {}
}
}get_indexing_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.
Get the current indexing status of a codebase. Shows progress percentage for actively indexing codebases and completion status for indexed codebases. It is categorised as a Read tool in the Claude Context MCP Server, which means it retrieves data without modifying state.
Register the Claude Context MCP server in PolicyLayer and add a rule for get_indexing_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 Claude Context. Nothing to install.
get_indexing_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 get_indexing_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 get_indexing_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.
get_indexing_status is provided by the Claude Context MCP server (zilliztech/claude-context). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Claude Context tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Claude Context tools catalogued and risk-classified — across an index of 42,500+ MCP servers.