Get information on a specific location in a file via LSP hover. Use this tool to retrieve detailed type information, documentation, and other contextual details about symbols in your code. Particularly useful for understanding variable types, function signatures, and module documentation at a spe...
AI agents call get_info_on_location to retrieve information from LSP MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries language server protocol for code information at a specific location. It performs information retrieval only—fetching hover data, type information, and documentation—without modifying, executing, or deleting any code or data. The requirement that 'the file be opened first' indicates it operates on already-loaded context.
From the tool's definition Tool retrieves LSP hover information including 'type information, documentation, and other contextual details' about code symbols.
Documented attack patterns abuse exactly the kind of access get_info_on_location gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LSP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_info_on_location:
{
"version": "1",
"default": "deny",
"tools": {
"get_info_on_location": {}
}
}get_info_on_location is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get information on a specific location in a file via LSP hover. Use this tool to retrieve detailed type information, documentation, and other contextual details about symbols in your code. Particularly useful for understanding variable types, function signatures, and module documentation at a specific location in the code. Use this whenever you need to get a better idea on what a particular function is doing in that context. Requires the file to be opened first. It is categorised as a Read tool in the LSP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LSP MCP Server MCP server in PolicyLayer and add a rule for get_info_on_location: 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 MCP Server. Nothing to install.
get_info_on_location 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 get_info_on_location 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 get_info_on_location. 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.
get_info_on_location is provided by the LSP MCP Server MCP server (tritlo/lsp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 LSP MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 LSP MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.