Get comprehensive information about a symbol in one call: type signature, definition location, all references, implementations, and call hierarchy. Use when you need full context about something instead of making multiple separate queries.
AI agents call lsp_smart_search 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 aggregates multiple language server queries to retrieve metadata about code symbols. It performs no writes, deletes, executions, or side effects. The worst-case misuse by an AI agent would be information disclosure about the codebase structure, which has minimal blast radius. Categorized as Read with low severity.
From the tool's definition lsp_smart_search retrieves 'type signature, definition location, all references, implementations, and call hierarchy'—all read operations.
Attacks that exploit this kind of access
Get comprehensive information about a symbol in one call: type signature, definition location, all references, implementations, and call hierarchy. Use when you need full context about something instead of making multiple separate queries. 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_smart_search: 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_smart_search 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_smart_search 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_smart_search. 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_smart_search 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 →