AI agents call lsp_document_symbols to retrieve information from Lsp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static analysis to extract metadata about code structure. It reads and parses existing code to produce a symbol table or AST outline, but does not modify, execute, or delete anything. The output is informational only. This is a typical LSP textDocument/documentSymbol request, which is a read-only introspection operation with no blast radius if misused by an agent.
From the tool's definition Tool retrieves a structured outline of symbols (functions, classes, interfaces, variables) from a file. The description explicitly states it 'Get[s]' information and is 'Faster and more accurate than reading and parsing the file yourself,' indicating pure…
Attacks that exploit this kind of access
Get a structured outline of a file: all functions, classes, interfaces, and variables with their types and relationships. Faster and more accurate than reading and parsing the file yourself. It is categorised as a Read tool in the Lsp MCP Server, which means it retrieves data without modifying state.
Register the Lsp 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 Lsp. Nothing to install.
lsp_document_symbols 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_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.
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.
lsp_document_symbols is provided by the Lsp MCP server (lsp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →