security_audit_licence_compatibility

SERVERDataNexus MCP SOURCEdev-7bd0/mcp-server

Low RISK CLASS

Category Read

Parameters 20 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-audit-licence-compatibility.md

WHAT IT DOES

What security_audit_licence_compatibility does on DataNexus MCP

AI agents call security_audit_licence_compatibility 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
`packages`	object	—	List of {name, ecosystem} dicts to check compatibility. Optional.
`spdx_ids`	object	—	List of SPDX licence identifiers to check compatibility. Optional.

Parameters from the server's own tool schema.

RISK

Why security_audit_licence_compatibility is rated Low

This tool performs read-only queries against licence databases and dependency services to assess compatibility. It retrieves information and provides analysis without side effects. Even though it accesses external services (deps.dev), the operation is a query/lookup, not an execution of arbitrary code or commands. The stated purpose is audit and compliance checking, which are informational activities.

From the tool's definition Tool audits licence compatibility by querying static SPDX tables and deps.dev data; returns verdicts (COMPATIBLE/CONFLICT) with no modifications to any system.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

security_audit_licence_compatibility Allowed

security_audit_licence_compatibility 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_audit_licence_compatibility": {}
  }
}

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

FAQ

Questions about security_audit_licence_compatibility

What does the security_audit_licence_compatibility tool do? +

Audit the licence compatibility of your entire dependency list. Input package names (with ecosystem) or SPDX IDs; get a COMPATIBLE/CONFLICT verdict with specific conflicting pairs and recommended action. Uses static SPDX compatibility table — no network call for spdx_ids path. Package path resolves licences from deps.dev (max 10 concurrent). Max 50 items. Rate limit: 60/minute. No auth required. For developers and compliance teams auditing open source licence risk before shipping. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="security_audit_licence_compatibility", 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_audit_licence_compatibility accept? +

security_audit_licence_compatibility accepts 2 parameters: packages, spdx_ids. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on security_audit_licence_compatibility? +

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

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

Can I rate-limit security_audit_licence_compatibility? +

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

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

security_audit_licence_compatibility 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

emit_second_audit on 0sec → The MCP Attack Database →

Guides

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