security_fetch_package_licence

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

WHAT IT DOES

What security_fetch_package_licence does on DataNexus MCP

AI agents call security_fetch_package_licence 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.

RISK

Why security_fetch_package_licence is rated Low

This tool queries dependency licence metadata without triggering side effects. It retrieves immutable, publicly available security/compliance data (SPDX identifiers). The description explicitly confirms read-only semantics and idempotency, placing it firmly in the Read category with low severity (minimal blast radius if misused—worst case is incorrect compliance decisions based on wrong licence data, but no…

From the tool's definition "Read-only. No side effects. Idempotent." Fetches and returns SPDX licence identifier for a package version from verified source (deps.dev). No data creation, modification, deletion, code execution, or financial operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

security_fetch_package_licence Allowed

security_fetch_package_licence 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_licence": {}
  }
}

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

FAQ

Questions about security_fetch_package_licence

What does the security_fetch_package_licence tool do? +

Fetch the SPDX licence identifier for an open source package version. Read-only. No side effects. Idempotent. package: Package name e.g. flask. Required. version: Exact version string e.g. 2.3.0. Required. ecosystem: One of PyPI, npm, Maven, Go, Cargo, NuGet, RubyGems. Required. Returns the SPDX licence identifier e.g. MIT, Apache-2.0, GPL-3.0. Use this to verify licence compatibility before including a dependency. Use security_fetch_package_vulnerabilities instead when checking for security issues not licences. 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_package_licence", 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_licence accept? +

security_fetch_package_licence accepts 3 parameters: package, version, 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_licence? +

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

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

Can I rate-limit security_fetch_package_licence? +

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

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

security_fetch_package_licence 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 →