Find identifier references by name across supported source files.
AI agents call find_references to retrieve information from Syntax Map without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static code analysis to locate where identifiers are used. It reads and searches indexed source files to return reference locations but does not execute code, modify files, or trigger external side effects. It is analogous to a 'find all references' feature in an IDE, which is a standard read-only analysis capability.
From the tool's definition Tool description states 'Find identifier references by name across supported source files' — a query operation that retrieves cross-file reference information without modifying code or executing arbitrary operations.
Attacks that exploit this kind of access
Find identifier references by name across supported source files. It is categorised as a Read tool in the Syntax Map MCP Server, which means it retrieves data without modifying state.
Register the Syntax Map 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 Syntax Map. 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 Syntax Map MCP server (kht6163/syntax-map-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 →