lsp_list_servers

List known language servers and whether their binary is on PATH.

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-list-servers.md

WHAT IT DOES

What lsp_list_servers does on LocalAnt

AI agents call lsp_list_servers 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_list_servers is rated Low

This is a read-only operation that queries the state of language servers on the system. It retrieves and displays information (which servers exist and whether their binaries are accessible) without creating, modifying, deleting, or executing anything. The blast radius is minimal—an AI agent misusing this tool could only learn what language servers are available, which poses no direct risk.

From the tool's definition Tool name 'lsp_list_servers' and description 'List known language servers and whether their binary is on PATH' indicate a retrieval/query operation that checks status of language servers without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs lsp_list_servers 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_list_servers, this is the rule to start with:

lsp_list_servers Allowed

lsp_list_servers 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_list_servers": {}
  }
}

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_list_servers call is checked against it from then on.

FAQ

Questions about lsp_list_servers

What does the lsp_list_servers tool do? +

List known language servers and whether their binary is on PATH. 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_list_servers? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for lsp_list_servers: 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_list_servers? +

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

Can I rate-limit lsp_list_servers? +

Yes. Add a rate_limit block to the lsp_list_servers 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_list_servers completely? +

Set action: deny in the PolicyLayer policy for lsp_list_servers. 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_list_servers? +

lsp_list_servers 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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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