Get TypeScript diagnostics (errors, warnings) for a file or project
AI agents call getDiagnostics to retrieve information from TypeScript LSP MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns diagnostic information about TypeScript code without creating, modifying, deleting, or executing any side effects. Diagnostics are informational outputs from the TypeScript compiler. Even though diagnostics may reveal issues in code, the tool itself performs no action on the codebase—it merely reports static analysis results, consistent with IDE diagnostic features.
From the tool's definition Tool name is 'getDiagnostics' and description states it retrieves TypeScript diagnostics (errors, warnings) for a file or project.
Attacks that exploit this kind of access
Get TypeScript diagnostics (errors, warnings) for a file or project. It is categorised as a Read tool in the TypeScript LSP MCP MCP Server, which means it retrieves data without modifying state.
Register the TypeScript LSP MCP server in PolicyLayer and add a rule for getDiagnostics: 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 TypeScript LSP MCP. Nothing to install.
getDiagnostics 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 getDiagnostics 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 getDiagnostics. 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.
getDiagnostics is provided by the TypeScript LSP MCP server (jaenster/ts-lsp-mcp). 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 →