AI agents call lsp_hover to retrieve information from LocalAnt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a language server (LSP) for static analysis metadata only. It has no side effects, does not execute code, does not modify data, and does not interact with external systems. It is purely informational retrieval, fitting the Read category with low severity due to its limited scope and passive nature.
From the tool's definition lsp_hover retrieves type/hover information for a symbol at a specified position in TypeScript/JavaScript code. It performs a read-only query to a language server, returning metadata about the symbol without modifying files or executing code.
Attacks that exploit this kind of access
Get type/hover info for the symbol at a 1-indexed line/character (TypeScript/JavaScript). It is categorised as a Read tool in the LocalAnt MCP Server, which means it retrieves data without modifying state.
Register the LocalAnt MCP server in PolicyLayer and add a rule for lsp_hover: 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 LocalAnt. Nothing to install.
lsp_hover 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_hover 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_hover. 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_hover is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
lsp_hover is one line of LocalAnt's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →