Trace where a type comes from and how it is composed
AI agents call traceType 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 retrieves type composition/origin information from the TypeScript Language Server. It performs read-only analysis of type information without modifying any data, executing code, or causing side effects.
From the tool's definition Trace where a type comes from and how it is composed
Attacks that exploit this kind of access
Trace where a type comes from and how it is composed. 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 traceType: 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.
traceType 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 traceType 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 traceType. 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.
traceType 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 →