dependency_vulnerability_scan

SERVERMcp Knowledge SOURCEhttps://mcp.gapup.io

Low RISK CLASS

Category Read

Parameters 52 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-getgapup-mcp-knowledge/dependency-vulnerability-scan.md

WHAT IT DOES

What dependency_vulnerability_scan does on Mcp Knowledge

AI agents call dependency_vulnerability_scan to retrieve information from Mcp Knowledge 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
`mode`	string	Yes	Manifest type: "package_json"=npm, "requirements_txt"=pip, "go_mod"=Go modules, "cargo_toml"=Rust, "composer_json"=PHP, "gem_lock"=Ruby, "sbom_cyclonedx"=Cyclon
`async`	boolean	—	If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti
`severity_min`	string	—	Minimum severity to include in results (default: "medium").
`manifest_content`	string	Yes	Raw text content of the manifest file to scan (e.g. full contents of package.json, requirements.txt, etc.).
`include_transitive`	boolean	—	Include transitive/indirect dependencies in results (default: true).

Parameters from the server's own tool schema.

RISK

Why dependency_vulnerability_scan is rated Low

This is a scanning and analysis tool that fetches vulnerability information from public databases (OSV.dev, NVD, CISA KEV) and reports findings. It has no side effects on the scanned project, does not execute code, does not modify dependencies, and does not delete anything.

From the tool's definition Tool 'dependency_vulnerability_scan' scans project dependency manifests and returns known vulnerabilities—it retrieves and queries vulnerability data from OSV.dev and NVD without modifying, executing, or deleting anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dependency_vulnerability_scan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Knowledge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dependency_vulnerability_scan, this is the rule to start with:

dependency_vulnerability_scan Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Knowledge, apply this rule, and every dependency_vulnerability_scan call is checked against it from then on.

FAQ

Questions about dependency_vulnerability_scan

What does the dependency_vulnerability_scan tool do? +

SCA (Software Composition Analysis) — scans a project dependency manifest and returns known vulnerabilities for each dependency. Supports: package.json (npm), requirements.txt (Python), go.mod (Go), Cargo.toml (Rust), composer.json (PHP), Gemfile.lock (Ruby), CycloneDX SBOM JSON. PRIMARY source: OSV.dev (keyless, free, covers npm/PyPI/Go/crates.io/Packagist/RubyGems + GHSA advisories federated). CVSS enrichment: NVD NIST (when OSV lacks score). Exploitation flag: CISA KEV (known-exploited-vulnerabilities catalog). Returns per-vuln CVE/GHSA IDs, severity, CVSS score, fixed version, and actionable upgrade recommendations. Relevant for EU NIS2 supply chain risk obligations, DORA, SOC 2 vendor assessments. Cache TTL 6h. Parallel OSV queries (concurrency=10). SLA <=30s p95. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.

What parameters does dependency_vulnerability_scan accept? +

dependency_vulnerability_scan accepts 5 parameters: mode, async, severity_min, manifest_content, include_transitive. Required: mode, manifest_content. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on dependency_vulnerability_scan? +

Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for dependency_vulnerability_scan: 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 Mcp Knowledge. Nothing to install.

What risk level is dependency_vulnerability_scan? +

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

Can I rate-limit dependency_vulnerability_scan? +

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

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

dependency_vulnerability_scan is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Knowledge, and thousands of servers like it.

This server

All 271 Mcp Knowledge tools →

Across the catalogue

The MCP Attack Database →

Guides

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