Find all references to a symbol at a position
AI agents call getReferences to retrieve information from TypeScript LSP MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
getReferences retrieves metadata about symbol usage within a codebase but does not create, modify, delete, or execute any code. The tool has no side effects and matches the Read category pattern of querying data without mutations. Low severity because querying references poses minimal risk even if misused by an agent—the worst outcome is information disclosure of code structure, not data loss or unwanted execution.
From the tool's definition "Find all references to a symbol at a position" - this tool queries type information and returns references without modifying code, files, or any other state. It is analogous to IDE 'Find References' functionality which is inherently read-only.
Attacks that exploit this kind of access
Find all references to a symbol at a position. It is categorised as a Read tool in the TypeScript LSP MCP MCP Server, which means it retrieves data without modifying state.
Register the TypeScript LSP MCP server in PolicyLayer and add a rule for getReferences: 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 TypeScript LSP MCP. Nothing to install.
getReferences 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 getReferences 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 getReferences. 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.
getReferences is provided by the TypeScript LSP MCP server (jaenster/ts-lsp-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 →