Find how two files/modules are connected in the dependency graph. When no direct path exists, returns visual context: nearest common ancestors, shared neighbors, community analysis, and bridge suggestions to help debug architectural silos. Args: source: Source file or module path. target: Target ...
AI agents call get_dependency_path to retrieve information from Repowise without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static analysis on a codebase's dependency graph to retrieve relationship information between files/modules. It has no side effects—it only queries and presents existing architectural data. No data is modified, deleted, or executed. This is a pure information retrieval operation.
From the tool's definition Tool description states it 'finds how two files/modules are connected' and 'returns visual context' including 'nearest common ancestors, shared neighbors, community analysis'.
Documented attack patterns abuse exactly the kind of access get_dependency_path gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Repowise, and nothing reaches the server without passing your rules. This is the rule we recommend for get_dependency_path:
{
"version": "1",
"default": "deny",
"tools": {
"get_dependency_path": {}
}
}get_dependency_path 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.
Find how two files/modules are connected in the dependency graph. When no direct path exists, returns visual context: nearest common ancestors, shared neighbors, community analysis, and bridge suggestions to help debug architectural silos. Args: source: Source file or module path. target: Target file or module path. repo: Repository path, name, or ID. It is categorised as a Read tool in the Repowise MCP Server, which means it retrieves data without modifying state.
Register the Repowise MCP server in PolicyLayer and add a rule for get_dependency_path: 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 Repowise. Nothing to install.
get_dependency_path 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_path 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_path. 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_path is provided by the Repowise MCP server (repowise-dev/repowise). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Repowise tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
19 Repowise tools catalogued and risk-classified — across an index of 42,500+ MCP servers.