security_fetch_dependency_graph
Fetch the full dependency tree for a package version including transitive dependencies. Read-only. No side effects. Idempotent. Hard 8-second timeout — large dependency trees may return partial results. package: Package name. Required. version: Exact version string e.g. 1.2.3. Required. ecosystem...
This record as markdown: /tools/dev-7bd0-mcp-server/security-fetch-dependency-graph.md
What security_fetch_dependency_graph does on DataNexus MCP
AI agents call security_fetch_dependency_graph to retrieve information from DataNexus MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
package | string | — | Package name e.g. requests. Required. |
version | string | — | Package version e.g. 2.28.0. Required. |
ecosystem | string | — | Package ecosystem: npm, pypi, cargo, go, maven, nuget. Required. |
Parameters from the server's own tool schema.
Why security_fetch_dependency_graph is rated Low
This tool retrieves and queries dependency graph data from a package ecosystem without any ability to modify, execute, or delete resources. The explicit statement of read-only semantics, idempotency, and no side effects clearly places it in the Read category. Low severity reflects that misuse would only expose information about supply chain dependencies, not enable destructive or financial actions.
From the tool's definition Tool is described as 'Read-only. No side effects. Idempotent.' It 'Fetch[es] the full dependency tree' and 'Returns all direct and transitive dependencies' — pure data retrieval operations with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs security_fetch_dependency_graph safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DataNexus MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For security_fetch_dependency_graph, this is the rule to start with:
security_fetch_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 DataNexus MCP, apply this rule, and every security_fetch_dependency_graph call is checked against it from then on.
Questions about security_fetch_dependency_graph
Fetch the full dependency tree for a package version including transitive dependencies. Read-only. No side effects. Idempotent. Hard 8-second timeout — large dependency trees may return partial results. package: Package name. Required. version: Exact version string e.g. 1.2.3. Required. ecosystem: One of PyPI, npm, Maven, Go, Cargo, NuGet, RubyGems. Required. Returns all direct and transitive dependencies with version constraints. Use this to understand full supply chain exposure. Use security_fetch_package_vulnerabilities instead when you only need CVEs for a single package. Verified source: deps.dev (Google). 1-hour cache. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="security_fetch_dependency_graph", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}". It is categorised as a Read tool in the DataNexus MCP MCP Server, which means it retrieves data without modifying state.
security_fetch_dependency_graph accepts 3 parameters: package, version, ecosystem. The full parameter table on this page comes from the server's own tool schema.
Register the DataNexus MCP server in PolicyLayer and add a rule for security_fetch_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 DataNexus MCP. Nothing to install.
security_fetch_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 security_fetch_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 security_fetch_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.
security_fetch_dependency_graph is provided by the DataNexus MCP server (dev-7bd0/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DataNexus, and thousands of servers like it.
This server
Across the catalogue