List all TypeScript dependencies available in the project (from package.json and node_modules). Shows which external libraries have TypeScript declarations that can be indexed.
AI agents call get_typescript_dependencies to retrieve information from TypeScript MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries project dependency metadata from package.json and node_modules, enabling inspection of available libraries and their TypeScript declaration status. It has no side effects, does not execute code, and cannot create, modify, or delete data.
From the tool's definition Tool description states 'List all TypeScript dependencies' and 'Shows which external libraries' — uses list/show verbs indicating data retrieval with no modification capability.
Documented attack patterns abuse exactly the kind of access get_typescript_dependencies gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TypeScript MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_typescript_dependencies:
{
"version": "1",
"default": "deny",
"tools": {
"get_typescript_dependencies": {}
}
}get_typescript_dependencies is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all TypeScript dependencies available in the project (from package.json and node_modules). Shows which external libraries have TypeScript declarations that can be indexed. It is categorised as a Read tool in the TypeScript MCP MCP Server, which means it retrieves data without modifying state.
Register the TypeScript MCP server in PolicyLayer and add a rule for get_typescript_dependencies: 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 MCP. Nothing to install.
get_typescript_dependencies 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 get_typescript_dependencies 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 get_typescript_dependencies. 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.
get_typescript_dependencies is provided by the TypeScript MCP server (mizchi/lsmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TypeScript MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 TypeScript MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.