dependency_graph
Return import/dependency relationships for a module.
This record as markdown: /tools/ashlesh-t-cognirepo/dependency-graph.md
What dependency_graph does on CogniRepo
AI agents call dependency_graph to retrieve information from CogniRepo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why dependency_graph is rated Low
This tool retrieves static analysis data (dependency relationships) from existing code or metadata. It performs a query/lookup operation with no side effects, no code execution, and no data modification. The verb 'Return' confirms it is a read operation. The blast radius if misused is minimal—an agent could at most learn about code structure, which is informational only.
From the tool's definition Tool name 'dependency_graph' and description 'Return import/dependency relationships for a module' indicate a retrieval operation that queries and returns information about module dependencies without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs dependency_graph safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CogniRepo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dependency_graph, this is the rule to start with:
dependency_graph 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 CogniRepo, apply this rule, and every dependency_graph call is checked against it from then on.
Questions about dependency_graph
Return import/dependency relationships for a module. It is categorised as a Read tool in the CogniRepo MCP Server, which means it retrieves data without modifying state.
Register the CogniRepo MCP server in PolicyLayer and add a rule for dependency_graph: 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 CogniRepo. Nothing to install.
dependency_graph 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 dependency_graph 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 dependency_graph. 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.
dependency_graph is provided by the CogniRepo MCP server (pypi:cognirepo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CogniRepo, and thousands of servers like it.
This server
Across the catalogue