AI agents call lsp_file_exports 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 queries and retrieves structural information about a file's exported symbols (functions, classes, interfaces, variables) without modifying, executing, or deleting anything. It is a pure Read operation with minimal blast radius—extracting public API metadata carries low security risk as it only surfaces information already defined in the codebase.
From the tool's definition Tool description states it 'Get[s] the public API surface of a file' and explicitly advises using it 'to understand what a module exposes without reading the entire file.' The verb 'Get' and the read-only intent confirm retrieval of metadata/symbols.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get the public API surface of a file: top-level functions, classes, interfaces, and variables with their type signatures. Use to understand what a module exposes without reading the entire file. 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_file_exports: 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_file_exports 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_file_exports 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_file_exports. 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_file_exports 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 →