dependency_vulnerability_scan
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: ...
This record as markdown: /tools/io-github-getgapup-gapup-mcp/dependency-vulnerability-scan.md
What dependency_vulnerability_scan does on Gapup Mcp
AI agents call dependency_vulnerability_scan to retrieve information from Gapup 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 |
|---|---|---|---|
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.
Why dependency_vulnerability_scan is rated Low
Dependency vulnerability scanning is fundamentally a read-only information-gathering operation. The tool analyzes local manifests (package.json, requirements.txt, etc.) against public vulnerability databases and reports findings. It does not execute code, modify files, delete data, or move funds.
From the tool's definition The tool 'scans a project dependency manifest and returns known vulnerabilities' — it retrieves and queries vulnerability data from OSV.dev, NVD, and CISA KEV without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs dependency_vulnerability_scan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gapup Mcp, 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 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 Gapup Mcp, apply this rule, and every dependency_vulnerability_scan call is checked against it from then on.
Questions about dependency_vulnerability_scan
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 Gapup Mcp MCP Server, which means it retrieves data without modifying state.
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.
Register the Gapup 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 Gapup Mcp. Nothing to install.
dependency_vulnerability_scan 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 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.
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.
dependency_vulnerability_scan is provided by the Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gapup, and thousands of servers like it.
This server
Across the catalogue