get_di_tree
Trace NestJS dependency injection tree (what a service injects + who injects it). Use to understand DI wiring for a specific provider. For module-level graph use get_module_graph instead. Read-only. Returns JSON: { service, injects: [{ name, kind }], injected_by: [{ name, kind }] }.
This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/get-di-tree.md
What get_di_tree does on Trace
AI agents call get_di_tree to retrieve information from Trace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_di_tree is rated Low
This tool retrieves and queries dependency injection metadata from NestJS applications to understand DI wiring patterns. It has no side effects, does not modify source code, execute commands, or trigger external operations. It is purely introspective analysis, fitting the Read category definition of 'retrieves or queries data; no side effects'.
From the tool's definition Tool description explicitly states 'Read-only' and 'Trace NestJS dependency injection tree'. Returns JSON data about service dependencies and injection relationships without modifying code or executing operations.
Attacks that exploit this kind of access
The rule that runs get_di_tree safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_di_tree, this is the rule to start with:
get_di_tree is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every get_di_tree call is checked against it from then on.
Questions about get_di_tree
Trace NestJS dependency injection tree (what a service injects + who injects it). Use to understand DI wiring for a specific provider. For module-level graph use get_module_graph instead. Read-only. Returns JSON: { service, injects: [{ name, kind }], injected_by: [{ name, kind }] }. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.
Register the Trace MCP server in PolicyLayer and add a rule for get_di_tree: 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 Trace. Nothing to install.
get_di_tree 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_di_tree 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_di_tree. 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_di_tree is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Trace, and thousands of servers like it.
This server
Across the catalogue