lsp_hover

Get type/hover info for the symbol at a 1-indexed line/character (TypeScript/JavaScript).

SERVERLocalAnt SOURCEyuga-hashimoto/localant

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yuga-hashimoto-localant/lsp-hover.md

WHAT IT DOES

What lsp_hover does on LocalAnt

AI agents call lsp_hover to retrieve information from LocalAnt without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why lsp_hover is rated Low

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

RECOMMENDED RULE

The rule that runs lsp_hover safely

PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lsp_hover, this is the rule to start with:

lsp_hover Allowed

lsp_hover is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lsp_hover": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect LocalAnt, apply this rule, and every lsp_hover call is checked against it from then on.

FAQ

Questions about lsp_hover

What does the lsp_hover tool do? +

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.

How do I enforce a policy on lsp_hover? +

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.

What risk level is lsp_hover? +

lsp_hover is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit lsp_hover? +

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.

How do I block lsp_hover completely? +

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.

What MCP server provides lsp_hover? +

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.

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →