Check the health and statistics of the CodeXRay index — total symbols, edges, files, languages, and index freshness.
AI agents call codexray_status to retrieve information from CodeXRay 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 retrieves diagnostic information about the state of a code knowledge graph index. It has no side effects, cannot modify data, execute code, or trigger external operations. It is a pure read operation that returns system metadata for informational purposes.
From the tool's definition Tool name 'codexray_status' and description explicitly states it 'checks the health and statistics' of an index, retrieving metadata like 'total symbols, edges, files, languages, and index freshness' with no modification or execution capability.
Documented attack patterns abuse exactly the kind of access codexray_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CodeXRay, and nothing reaches the server without passing your rules. This is the rule we recommend for codexray_status:
{
"version": "1",
"default": "deny",
"tools": {
"codexray_status": {}
}
} codexray_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.
Check the health and statistics of the CodeXRay index — total symbols, edges, files, languages, and index freshness. It is categorised as a Read tool in the CodeXRay MCP Server, which means it retrieves data without modifying state.
Register the CodeXRay MCP server in PolicyLayer and add a rule for codexray_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 CodeXRay. Nothing to install.
codexray_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 codexray_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 codexray_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.
codexray_status is provided by the CodeXRay MCP server (neuralrays/codexray). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CodeXRay, 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.
16 CodeXRay tools catalogued and risk-classified — across an index of 43,000+ MCP servers.