List every textual occurrence of a named symbol in the indexed
AI agents call find_references to retrieve information from Code Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only search across a codebase to find textual occurrences of a symbol. It retrieves data (reference locations) with no side effects, state changes, or code execution. The action is analogous to a grep or find operation in version control systems, making it a Read category tool with low severity.
From the tool's definition Tool description states 'List every textual occurrence of a named symbol in the indexed' — a query/search operation that retrieves symbol references without modifying or executing code.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List every textual occurrence of a named symbol in the indexed. It is categorised as a Read tool in the Code Context MCP Server, which means it retrieves data without modifying state.
Register the Code Context MCP server in PolicyLayer and add a rule for find_references: 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 Code Context. Nothing to install.
find_references 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 find_references 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 find_references. 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.
find_references is provided by the Code Context MCP server (nachogeinfor-ops/code-context). 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 →