vuln_patch_priority_engine
As a CTO, quickly prioritize unpatched CVEs by combining exploitability scores (EPSS) with cloud asset criticality. Input a list of CVE IDs and your AWS service types (e.g., EC2, RDS) to receive a ranked patching order with risk scores and estimated cloud impact. Uses public NVD, OpenCVE, and AWS...
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/vuln-patch-priority-engine.md
What vuln_patch_priority_engine does on Mcp Knowledge
AI agents call vuln_patch_priority_engine 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 |
|---|---|---|---|
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 |
cveIds | array | Yes | List of CVE identifiers to analyze (e.g., ["CVE-2021-44228", "CVE-2023-3824"]) |
maxResults | number | — | Maximum number of prioritized CVEs to return (default: 10) |
awsServices | array | — | AWS service types affected by these CVEs (e.g., ["EC2", "RDS", "Lambda"]) |
Parameters from the server's own tool schema.
Why vuln_patch_priority_engine is rated Low
This tool reads and aggregates public vulnerability data (NVD, OpenCVE, EPSS scores) and AWS pricing data to produce a ranked list/report. It does not modify, execute, or delete anything — it is a read/query/analysis tool. Severity is medium because it processes sensitive security posture information (CVE IDs, AWS service types) that could reveal exploitable weaknesses if misused.
From the tool's definition prioritize unpatched CVEs by combining exploitability scores (EPSS) with cloud asset criticality... ranked patching order with risk scores and estimated cloud impact. Uses public NVD, OpenCVE, and AWS pricing data
Attacks that exploit this kind of access
The rule that runs vuln_patch_priority_engine 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 vuln_patch_priority_engine, this is the rule to start with:
vuln_patch_priority_engine 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 Mcp Knowledge, apply this rule, and every vuln_patch_priority_engine call is checked against it from then on.
Questions about vuln_patch_priority_engine
As a CTO, quickly prioritize unpatched CVEs by combining exploitability scores (EPSS) with cloud asset criticality. Input a list of CVE IDs and your AWS service types (e.g., EC2, RDS) to receive a ranked patching order with risk scores and estimated cloud impact. Uses public NVD, OpenCVE, and AWS pricing data. Ideal for vulnerability management and cloud security posture improvement. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.
vuln_patch_priority_engine accepts 4 parameters: async, cveIds, maxResults, awsServices. Required: cveIds. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for vuln_patch_priority_engine: 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.
vuln_patch_priority_engine 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 vuln_patch_priority_engine 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 vuln_patch_priority_engine. 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.
vuln_patch_priority_engine 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.
More on Mcp Knowledge, and thousands of servers like it.
This server
Across the catalogue