Find a symbol by name alone—no file path or position needed. Returns the definition location plus full context (type info, references, call hierarchy). Use when you know a symbol name but not where it is defined.
AI agents call lsp_find_symbol 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.
lsp_find_symbol is a Language Server Protocol query that retrieves information about code symbols (their location, type info, references, call hierarchy). It performs no writes, deletions, or code execution—only reads and returns static code analysis data. This is a standard IDE navigation feature with negligible risk if misused by an AI agent.
From the tool's definition Tool description states it 'Find[s] a symbol by name' and 'Returns the definition location plus full context'—pure retrieval of metadata and code context with no modification or execution.
Attacks that exploit this kind of access
Find a symbol by name alone—no file path or position needed. Returns the definition location plus full context (type info, references, call hierarchy). Use when you know a symbol name but not where it is defined. 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_symbol: 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_symbol 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_symbol 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_symbol. 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_symbol 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 →