AI agents call lsp_find_references to retrieve information from Lsp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs semantic analysis to locate symbol references throughout a codebase. It retrieves information about where symbols are used but does not modify, execute, delete, or affect any code or data. It is a read-only operation that assists in code comprehension and impact analysis prior to potential modifications. The high confidence reflects the clear read-only nature of the operation.
From the tool's definition Tool description states 'Find every usage of a symbol across the codebase' and explicitly notes it is 'More complete than grep—finds semantic matches'.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Find every usage of a symbol across the codebase. Use before renaming or deleting to understand impact. More complete than grep—finds semantic matches, not just text. It is categorised as a Read tool in the Lsp MCP Server, which means it retrieves data without modifying state.
Register the Lsp MCP server in PolicyLayer and add a rule for lsp_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 Lsp. Nothing to install.
lsp_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 lsp_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 lsp_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.
lsp_find_references is provided by the Lsp MCP server (lsp-mcp-server). 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 →