security_fetch_package_vulnerabilities

SERVERDataNexus MCP SOURCEdev-7bd0/mcp-server

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-7bd0-mcp-server/security-fetch-package-vulnerabilities.md

WHAT IT DOES

What security_fetch_package_vulnerabilities does on DataNexus MCP

AI agents call security_fetch_package_vulnerabilities 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`	object	—	Package name e.g. requests. Required in single-package mode.
`version`	object	—	Package version e.g. 2.28.0. Required in single-package mode.
`packages`	object	—	Batch list of {name, version, ecosystem} objects. Max 50.
`ecosystem`	object	—	Package ecosystem: npm, pypi, cargo, go, maven, nuget. Required.

Parameters from the server's own tool schema.

RISK

Why security_fetch_package_vulnerabilities is rated Low

This tool retrieves vulnerability information about software packages from verified public data sources. It performs a query-only operation with no ability to modify data, execute code, or trigger external operations. The read-only nature, absence of side effects, and idempotent design confirm this is a Read category tool.

From the tool's definition Tool description explicitly states 'Read-only. No side effects. Idempotent.' and fetches CVE vulnerability data from public open-source package registries (PyPI, npm, Maven, Go, Cargo, NuGet, RubyGems).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs security_fetch_package_vulnerabilities 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_package_vulnerabilities, this is the rule to start with:

security_fetch_package_vulnerabilities Allowed

security_fetch_package_vulnerabilities is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "security_fetch_package_vulnerabilities": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect DataNexus MCP, apply this rule, and every security_fetch_package_vulnerabilities call is checked against it from then on.

FAQ

Questions about security_fetch_package_vulnerabilities

What does the security_fetch_package_vulnerabilities tool do? +

Fetch all known CVEs for an open source package version or a batch of packages. Read-only. No side effects. Idempotent. Single-package mode: package (e.g. requests), version (e.g. 2.28.0), ecosystem (PyPI/npm/Maven/Go/Cargo/NuGet/RubyGems). Batch mode: packages array of {name, version, ecosystem} objects — max 50 per call. If packages array is provided and non-empty, batch mode is used and package/version/ecosystem are ignored. Batch returns {results: [...], partial: bool, failed_count: int}. Each result has vuln_count and vulnerabilities list. Returns CVE ID, severity, CVSS score, affected range, and fixed version. Use security_fetch_cve_detail for full detail by CVE ID. Use security_audit_sbom_vulnerabilities for SBOM files. Verified source: Google OSV.dev. 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_package_vulnerabilities", 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.

What parameters does security_fetch_package_vulnerabilities accept? +

security_fetch_package_vulnerabilities accepts 4 parameters: package, version, packages, ecosystem. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on security_fetch_package_vulnerabilities? +

Register the DataNexus MCP server in PolicyLayer and add a rule for security_fetch_package_vulnerabilities: 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_package_vulnerabilities? +

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

Can I rate-limit security_fetch_package_vulnerabilities? +

Yes. Add a rate_limit block to the security_fetch_package_vulnerabilities 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_package_vulnerabilities completely? +

Set action: deny in the PolicyLayer policy for security_fetch_package_vulnerabilities. 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_package_vulnerabilities? +

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

KEEP EXPLORING

More on DataNexus, and thousands of servers like it.

This server

All 55 DataNexus tools →

Across the catalogue

fetch_url on 0sec → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →