Skip to main content
Glama

Patchfirst

List exploited CVEs

list_exploited
Read-onlyIdempotent

Top known-exploited CVEs (CISA KEV) ranked by Patchfirst priority, optionally filtered to known ransomware use, an ATT&CK tactic (e.g. "initial-access", "Privilege Escalation", "TA0004") or a technique id. Each result lists its techniques with provenance badges.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_exploited"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 10, max 25.
tacticNoATT&CK tactic id, name or TA id. One of: reconnaissance, resource-development, initial-access, execution, persistence, privilege-escalation, defense-evasion, stealth, defense-impairment, credential-access, discovery, lateral-movement, collection, command-and-control, exfiltration, impact
techniqueNoATT&CK technique id, e.g. "T1190"; parent ids include sub-techniques.
ransomware_onlyNoOnly KEV entries with known ransomware campaign use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description adds genuine context beyond that: results are ranked by a named priority model (Patchfirst) and each entry exposes techniques with provenance badges, which compensates for the absent output schema. It doesn't mention pagination or what happens beyond the top-N cut.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, with the core identity (top exploited CVEs, ranked) front-loaded and the filter options following. Every clause carries information an agent would otherwise lack.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

All four optional parameters are documented in-schema, annotations cover safety, and the description supplies the return-shape detail that no output schema provides (techniques plus provenance badges). Missing only minor operational detail such as ordering guarantees under filtering or behavior when no filters match.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description does add a small amount: it shows tactic accepts display-style values like 'Privilege Escalation' and 'TA0004', hinting at accepted formats beyond the lowercase slug list in the schema, and clarifies that technique filtering uses ids. That is marginal value over a fully documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (list) and a precise resource: CISA KEV known-exploited CVEs ranked by Patchfirst priority. It implicitly separates itself from cves_for_technique by emphasizing ranked top-N listing rather than a mapping lookup, but it never names or contrasts a sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the optional filters (ransomware, ATT&CK tactic, technique id) and the 'top ranked' framing, which suggests a prioritization use case. There is no explicit when-to-use / when-not statement, nor any routing to search, list_feed, or cves_for_technique when a different access pattern is wanted.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources