calculate_risk_score

THE RISK

Low Risk

Why calculate_risk_score needs a policy

This tool retrieves and synthesizes already-available vulnerability intelligence data (CVSS, EPSS, KEV, PoC indicators) to produce a risk score. It has no side effects, does not modify data, execute arbitrary code, delete resources, or trigger financial transactions. It is a pure analytical/read operation that correlates existing vulnerability metrics.

From the tool's definition Tool name and description indicate calculation and analysis of existing security data: 'Calculate a composite 0-100 risk score using CVSS, EPSS, KEV, and PoC data.' This performs aggregation and scoring of vulnerability metrics without querying external…

Documented attack patterns abuse exactly the kind of access calculate_risk_score gives an agent:

POLICY

How to control calculate_risk_score

PolicyLayer is an MCP gateway — it sits between your AI agents and CVE MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for calculate_risk_score:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "calculate_risk_score": {}
  }
}

calculate_risk_score is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register CVE MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More CVE MCP Server tools

Read parse_cvss Parse and explain a CVSS vector string (v2, v3.x, or v4.0). Args: vector: CVS Read check_exploit_availability Search GitHub for public proof-of-concept (PoC) exploit repositories for a CVE. Result Read check_ip_reputation Check an IP address reputation via AbuseIPDB and GreyNoise Community. Returns abuse co Read check_kev Check if a CVE is in the CISA Known Exploited Vulnerabilities (KEV) catalog. Args: Read check_package_vulns Check a package for known vulnerabilities via OSV.dev. Args: package: Package Read check_poc_exists Search for proof-of-concept exploits across GitHub, Exploit-DB, and Nuclei templates. Read check_ransomware_intel Check if a Bitcoin address is associated with a known ransomware family using the Rans Read check_url_safety Check a URL or domain for malicious activity via URLScan.io. Returns scan verdicts, ma

All 27 CVE MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about calculate_risk_score

What does the calculate_risk_score tool do? +

Calculate a composite 0-100 risk score using CVSS, EPSS, KEV, and PoC data. It is categorised as a Read tool in the CVE MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on calculate_risk_score? +

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

What risk level is calculate_risk_score? +

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

Can I rate-limit calculate_risk_score? +

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

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

calculate_risk_score is provided by the CVE MCP Server MCP server (mukul975/cve-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CVE MCP Server tool call.

Start from CVE MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →