lsp_document_symbols

List the symbols declared in a TypeScript/JavaScript file.

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-document-symbols.md

WHAT IT DOES

What lsp_document_symbols does on LocalAnt

AI agents call lsp_document_symbols 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_document_symbols is rated Low

This tool performs static analysis to extract and list symbols (functions, classes, variables, etc.) from a file without modifying or executing any code. It is a query operation with no side effects, making it a Read category tool with low severity risk.

From the tool's definition Tool name 'lsp_document_symbols' and description 'List the symbols declared in a TypeScript/JavaScript file' indicate a read-only operation that queries and retrieves symbol information from source code.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

lsp_document_symbols Allowed

lsp_document_symbols 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_document_symbols": {}
  }
}

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

FAQ

Questions about lsp_document_symbols

What does the lsp_document_symbols tool do? +

List the symbols declared in a TypeScript/JavaScript file. 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_document_symbols? +

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

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

Can I rate-limit lsp_document_symbols? +

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

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

lsp_document_symbols 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 →