Low Risk

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...

Part of the DataNexus MCP server.

security_fetch_dependency_graph is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE DATANEXUS MCP →

Free to start. No card required.

AI agents call security_fetch_dependency_graph to retrieve information from DataNexus MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though security_fetch_dependency_graph only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "security_fetch_dependency_graph": {}
  }
}

See the full DataNexus MCP policy for all 55 tools.

Get this rule live on your own DataNexus MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DATANEXUS MCP →

View all 55 tools →

These attack patterns abuse exactly the kind of access security_fetch_dependency_graph gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so security_fetch_dependency_graph only ever does what you allow.

SECURE DATANEXUS MCP →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the security_fetch_dependency_graph tool do? +

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.

How do I enforce a policy on security_fetch_dependency_graph? +

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.

What risk level is security_fetch_dependency_graph? +

security_fetch_dependency_graph is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit security_fetch_dependency_graph? +

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.

How do I block security_fetch_dependency_graph completely? +

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.

What MCP server provides security_fetch_dependency_graph? +

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.

Enforce policy on every DataNexus MCP tool call.

Deterministic rules across all 55 DataNexus MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.