Build comprehensive task-relevant context for a coding task. Analyzes your query, finds relevant symbols, includes their code snippets, call relationships, and dependency info. This is the MOST POWERFUL tool — use it to understand code needed for a task instead of reading multiple files.
AI agents call codexray_context 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 queries a pre-built semantic knowledge graph to retrieve code context, symbols, snippets, and relationships. It reads and aggregates information without modifying, executing, or deleting anything. Severity is medium because it can expose broad swaths of codebase structure and logic, which could be sensitive intellectual property, but there are no write or execute side effects.
From the tool's definition 'Build comprehensive task-relevant context for a coding task. Analyzes your query, finds relevant symbols, includes their code snippets, call relationships, and dependency info' — purely retrieval and analysis of existing code
Documented attack patterns abuse exactly the kind of access codexray_context 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_context:
{
"version": "1",
"default": "deny",
"tools": {
"codexray_context": {}
}
} codexray_context 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.
Build comprehensive task-relevant context for a coding task. Analyzes your query, finds relevant symbols, includes their code snippets, call relationships, and dependency info. This is the MOST POWERFUL tool — use it to understand code needed for a task instead of reading multiple files. 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_context: 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_context 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_context 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_context. 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_context 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.