Render dependency diagram for a file/directory path as Mermaid or DOT. Input: a path like
AI agents call get_dependency_diagram to retrieve information from Trace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access get_dependency_diagram gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trace, and nothing reaches the server without passing your rules. This is the rule we recommend for get_dependency_diagram:
{
"version": "1",
"default": "deny",
"tools": {
"get_dependency_diagram": {}
}
}get_dependency_diagram 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.
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.
Deterministic rules across all 178 Trace tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
178 Trace tools catalogued and risk-classified — across an index of 42,500+ MCP servers.