security_audit_sbom_license_policy

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-sbom-license-policy.md

WHAT IT DOES

What security_audit_sbom_license_policy does on DataNexus MCP

AI agents call security_audit_sbom_license_policy 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
`sbom`	string	—	CycloneDX or SPDX SBOM as JSON string. Required. 500 KB max.
`policy`	object	—	Policy dict with block/warn/allow arrays of SPDX licence IDs. Optional.

Parameters from the server's own tool schema.

RISK

Why security_audit_sbom_license_policy is rated Low

This tool retrieves and analyzes existing SBOM data against a license policy framework, returning a compliance assessment. It performs no data creation, modification, deletion, code execution, or financial operations. The audit function is purely informational—it reads the SBOM input and policy configuration, then returns classification results.

From the tool's definition Tool description states it performs 'Audit...and return a PASS/WARN/BLOCK verdict' and 'Returns verdict...blocked_packages, warned_packages, and the policy applied.' The tool analyzes and reports on SBOM license compliance without modifying data, executing…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

security_audit_sbom_license_policy Allowed

security_audit_sbom_license_policy 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_sbom_license_policy": {}
  }
}

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

FAQ

Questions about security_audit_sbom_license_policy

What does the security_audit_sbom_license_policy tool do? +

Audit a CycloneDX or SPDX SBOM against an SPDX licence policy and return a PASS/WARN/BLOCK verdict. sbom: Full SBOM as a JSON string — CycloneDX or SPDX format. Required. 500 KB max. policy: Optional dict with block/warn/allow arrays of exact SPDX licence identifiers (e.g. GPL-3.0, MIT). Defaults to block GPL-3.0 and AGPL-3.0, warn LGPL-2.1/MPL-2.0/BSD-4-Clause, allow MIT/Apache-2.0/BSD-2-Clause/BSD-3-Clause. No glob patterns — exact SPDX IDs only. Unlisted licences default to WARN. Returns verdict (PASS/WARN/BLOCK), blocked_packages, warned_packages, and the policy applied. Use security_audit_sbom_vulnerabilities for CVE auditing instead. Sources: deps.dev (Google). 1-hour cache per package. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="security_audit_sbom_license_policy", 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_sbom_license_policy accept? +

security_audit_sbom_license_policy accepts 2 parameters: sbom, policy. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on security_audit_sbom_license_policy? +

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

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

Can I rate-limit security_audit_sbom_license_policy? +

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

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

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