security_fetch_cve_epss
EPSS exploit probability score for a CVE — predicts likelihood of exploitation in the next 30 days. cve_id: CVE identifier e.g. "CVE-2021-44228". Returns: epss (float 0.0–1.0) and percentile (float 0.0–100.0). Thresholds: >0.7 patch immediately, 0.3–0.7 patch soon, <0.3 monitor. Use with security...
This record as markdown: /tools/dev-7bd0-mcp-server/security-fetch-cve-epss.md
What security_fetch_cve_epss does on DataNexus MCP
AI agents call security_fetch_cve_epss 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 |
|---|---|---|---|
cve_id | string | — | CVE identifier e.g. CVE-2021-44228. Required. |
Parameters from the server's own tool schema.
Why security_fetch_cve_epss is rated Low
This is a read-only data retrieval operation that queries a public, verified security database to obtain exploit probability metrics. It has no side effects, cannot modify data, cannot execute code, and poses minimal risk even if misused by an agent—worst case, it returns irrelevant risk scores that do not directly impact systems.
From the tool's definition Tool fetches and returns EPSS exploit probability score data from FIRST.org for a given CVE identifier. Returns only epss (float) and percentile (float) values. No modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs security_fetch_cve_epss 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_fetch_cve_epss, this is the rule to start with:
security_fetch_cve_epss 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 DataNexus MCP, apply this rule, and every security_fetch_cve_epss call is checked against it from then on.
Questions about security_fetch_cve_epss
EPSS exploit probability score for a CVE — predicts likelihood of exploitation in the next 30 days. cve_id: CVE identifier e.g. "CVE-2021-44228". Returns: epss (float 0.0–1.0) and percentile (float 0.0–100.0). Thresholds: >0.7 patch immediately, 0.3–0.7 patch soon, <0.3 monitor. Use with security_fetch_cve_detail to prioritize patching — EPSS measures urgency, CVSS measures severity. Source: FIRST.org. 6-hour cache. Example: fetch_cve_epss(cve_id="CVE-2021-44228"). It is categorised as a Read tool in the DataNexus MCP MCP Server, which means it retrieves data without modifying state.
security_fetch_cve_epss accepts 1 parameter: cve_id. The full parameter table on this page comes from the server's own tool schema.
Register the DataNexus MCP server in PolicyLayer and add a rule for security_fetch_cve_epss: 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.
security_fetch_cve_epss 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 security_fetch_cve_epss 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 security_fetch_cve_epss. 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.
security_fetch_cve_epss 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.
More on DataNexus, and thousands of servers like it.
This server
Across the catalogue