security_fetch_licence_analysis
Understand any software licence in plain English. Returns obligations, permissions, limitations, risk level, and OSI/FSF status for any SPDX licence identifier. Static bundle covers top-50 common licences (no network call). Falls back to spdx.org API for rare identifiers. All risk levels assume p...
This record as markdown: /tools/dev-7bd0-mcp-server/security-fetch-licence-analysis.md
What security_fetch_licence_analysis does on DataNexus MCP
AI agents call security_fetch_licence_analysis 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 |
|---|---|---|---|
spdx_id | string | — | SPDX licence identifier e.g. MIT, Apache-2.0, GPL-3.0. Required. |
Parameters from the server's own tool schema.
Why security_fetch_licence_analysis is rated Low
This is a read-only information retrieval tool that queries and returns license analysis data without any side effects. It does not create, modify, delete, execute code, or trigger external operations.
From the tool's definition Tool performs static analysis and lookup of software license information from SPDX identifiers. Returns 'obligations, permissions, limitations, risk level, and OSI/FSF status' - all informational outputs with no modifications to data or systems.
Attacks that exploit this kind of access
The rule that runs security_fetch_licence_analysis 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_licence_analysis, this is the rule to start with:
security_fetch_licence_analysis 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_licence_analysis call is checked against it from then on.
Questions about security_fetch_licence_analysis
Understand any software licence in plain English. Returns obligations, permissions, limitations, risk level, and OSI/FSF status for any SPDX licence identifier. Static bundle covers top-50 common licences (no network call). Falls back to spdx.org API for rare identifiers. All risk levels assume proprietary/commercial use. Rate limit: 60/minute. No auth required. For security engineers and developers understanding what a licence allows before including a dependency. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="security_fetch_licence_analysis", 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_licence_analysis accepts 1 parameter: spdx_id. 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_licence_analysis: 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_licence_analysis 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_licence_analysis 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_licence_analysis. 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_licence_analysis 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