security_fetch_package_risk_brief

SERVERDataNexus MCP SOURCEdev-7bd0/mcp-server

Low RISK CLASS

Category Read

Parameters 30 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-risk-brief.md

WHAT IT DOES

What security_fetch_package_risk_brief does on DataNexus MCP

AI agents call security_fetch_package_risk_brief 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
`version`	object	—	Package version e.g. 2.28.0. Required.
`ecosystem`	string	—	Package ecosystem: npm, pypi, cargo, go, maven. Required.
`package_name`	string	—	Package name e.g. requests. Required.

Parameters from the server's own tool schema.

RISK

Why security_fetch_package_risk_brief is rated Low

This tool performs security assessment queries against package registries and vulnerability databases, aggregating pre-computed verdicts and metadata. While it informs high-stakes decisions (package inclusion), the tool itself only reads and returns existing data — no side effects, code execution, or mutations.

From the tool's definition Tool description states it "returns verdict (SHIP/CAUTION/BLOCK), critical_cve_count, high_cve_count, licence_risk, maintainer_health, transitive_count, resolved_version, upstream_status, and reasoning" — clearly retrieval and aggregation of security metadata…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

security_fetch_package_risk_brief Allowed

security_fetch_package_risk_brief 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_risk_brief": {}
  }
}

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_risk_brief call is checked against it from then on.

FAQ

Questions about security_fetch_package_risk_brief

What does the security_fetch_package_risk_brief tool do? +

Single SHIP/CAUTION/BLOCK verdict for any package. Combines CVEs, licence, maintainer health, and transitive count in one call. Uses OSV.dev, deps.dev, PyPI, and npm registry — data refreshed on each call. Returns verdict (SHIP/CAUTION/BLOCK), critical_cve_count, high_cve_count, licence_risk, maintainer_health, transitive_count, resolved_version, upstream_status, and reasoning. Rate limit: 30/minute. No auth required. For security engineers performing pre-inclusion package review. 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_risk_brief", 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_risk_brief accept? +

security_fetch_package_risk_brief accepts 3 parameters: version, ecosystem, package_name. 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_risk_brief? +

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

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

Can I rate-limit security_fetch_package_risk_brief? +

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

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

security_fetch_package_risk_brief 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

aiva_get_churn_risk on AIVA MCP Server →fetch_url on 0sec → The MCP Attack Database →

Guides

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