Get current indexing status: state, statistics, and progress.
AI agents call get_indexing_status to retrieve information from Codebase Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns information about the current state of a codebase indexing process. There are no side effects, no data modification, no code execution, and no irreversible operations. It is purely informational retrieval, fitting the 'Read' category.
From the tool's definition Tool name 'get_indexing_status' and description 'Get current indexing status: state, statistics, and progress' indicate a read-only operation that retrieves status information without modifying, executing, or affecting any systems.
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 Codebase 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 current indexing status: state, statistics, and progress. It is categorised as a Read tool in the Codebase Context MCP Server, which means it retrieves data without modifying state.
Register the Codebase 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 Codebase 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 Codebase Context MCP server (patricksys/codebase-context). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Codebase Context tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 Codebase Context tools catalogued and risk-classified — across an index of 42,500+ MCP servers.