🚀 NEW: Dependency-aware context. Visualize and retrieve dependency tree for a symbol. Shows what code depends on what. Use this to understand code architecture and flow. Returns visual tree + grouped dependencies.
AI agents call get_dependency_tree to retrieve information from MCP Context Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays dependency information about code symbols. It performs read-only queries to understand code architecture and relationships. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an AI agent could only waste tokens or retrieve incorrect architectural understanding, not cause system damage or data loss.
From the tool's definition Tool name 'get_dependency_tree' and description state it 'Visualize and retrieve dependency tree' and 'Shows what code depends on what' — purely informational operations with no modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access get_dependency_tree gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Context Manager, and nothing reaches the server without passing your rules. This is the rule we recommend for get_dependency_tree:
{
"version": "1",
"default": "deny",
"tools": {
"get_dependency_tree": {}
}
}get_dependency_tree 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.
🚀 NEW: Dependency-aware context. Visualize and retrieve dependency tree for a symbol. Shows what code depends on what. Use this to understand code architecture and flow. Returns visual tree + grouped dependencies. It is categorised as a Read tool in the MCP Context Manager MCP Server, which means it retrieves data without modifying state.
Register the MCP Context Manager MCP server in PolicyLayer and add a rule for get_dependency_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 MCP Context Manager. Nothing to install.
get_dependency_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_dependency_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_dependency_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_dependency_tree is provided by the MCP Context Manager MCP server (transparentlyok/mcp-context-manager). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Context Manager, 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.
21 MCP Context Manager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.