Get the indexing status and statistics for registered codebases.
AI agents call get_index_status to retrieve information from Ue Codegraph without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries indexing status and statistics without modifying, executing code, or causing destructive operations. It is purely informational metadata retrieval, consistent with the Read category. Low severity because exposure of indexing status poses minimal risk—it cannot alter code, execute operations, or access sensitive data beyond public codebase statistics.
From the tool's definition Tool name 'get_index_status' and description 'Get the indexing status and statistics for registered codebases' indicate read-only retrieval of metadata about indexing progress and codebase statistics.
Attacks that exploit this kind of access
Get the indexing status and statistics for registered codebases. It is categorised as a Read tool in the Ue Codegraph MCP Server, which means it retrieves data without modifying state.
Register the Ue Codegraph MCP server in PolicyLayer and add a rule for get_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 Ue Codegraph. Nothing to install.
get_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 get_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 get_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.
get_index_status is provided by the Ue Codegraph MCP server (yomenstyle/ue-codegraph-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 →