Check the health of the CVE MCP server: NVD connectivity, KEV catalog status, and cache statistics. Note: This tool pings NVD without rate limiting — do not call it in a loop.
AI agents call health_check to retrieve information from CVE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a monitoring/diagnostic tool that retrieves system status information. It only reads and reports on the health of internal systems and external API connectivity, with no capability to modify, delete, execute operations, or commit financial actions. The severity is low because misuse would only result in redundant API calls (hence the warning about rate limiting) but no meaningful data loss or security breach.
From the tool's definition Tool performs health checks that query connectivity status and cache statistics ('pings NVD', 'KEV catalog status', 'cache statistics'); these are read-only diagnostic operations with no side effects or data modification.
Documented attack patterns abuse exactly the kind of access health_check gives an agent:
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 health_check:
{
"version": "1",
"default": "deny",
"tools": {
"health_check": {}
}
}health_check is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check the health of the CVE MCP server: NVD connectivity, KEV catalog status, and cache statistics. Note: This tool pings NVD without rate limiting — do not call it in a loop. It is categorised as a Read tool in the CVE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CVE MCP Server MCP server in PolicyLayer and add a rule for health_check: 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.
health_check 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 health_check 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 health_check. 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.
health_check 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.
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.
Free to start. No card required.
27 CVE MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.