get_dependency_diagram
Render dependency diagram for a file/directory path as Mermaid or DOT. Input: a path like
This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/get-dependency-diagram.md
What get_dependency_diagram does on Trace
AI agents call get_dependency_diagram 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_dependency_diagram is rated Low
This tool queries and displays dependency information from source code without modifying, executing, or deleting anything. It performs static analysis visualization only, making it a Read operation with low severity—misuse would only expose information architecture, not cause damage or unwanted side effects.
From the tool's definition Tool description states 'Render dependency diagram' which is a retrieval and visualization operation. The input is merely a path specification for reading an existing code structure, with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs get_dependency_diagram 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_dependency_diagram, this is the rule to start with:
get_dependency_diagram 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_dependency_diagram call is checked against it from then on.
Questions about get_dependency_diagram
Render dependency diagram for a file/directory path as Mermaid or DOT. Input: a path like. 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_dependency_diagram: 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_dependency_diagram 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_dependency_diagram 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_dependency_diagram. 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_dependency_diagram 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