Search GitHub for public proof-of-concept (PoC) exploit repositories for a CVE. Results are sorted by star count to surface the most credible exploits first. Args: cve_id: CVE identifier (e.g. CVE-2021-44228)
AI agents call check_exploit_availability 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 tool performs a read-only search across GitHub repositories to gather intelligence about publicly available exploits for a given CVE. While the underlying exploits themselves may be executable, the tool itself only reads and retrieves information. It does not execute code, modify data, delete resources, or trigger external operations.
From the tool's definition The tool description states it 'Search[es] GitHub for public proof-of-concept (PoC) exploit repositories' and 'Results are sorted by star count.' This is a query operation that retrieves and surfaces information without modifying, executing, or deleting…
Documented attack patterns abuse exactly the kind of access check_exploit_availability 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 check_exploit_availability:
{
"version": "1",
"default": "deny",
"tools": {
"check_exploit_availability": {}
}
}check_exploit_availability 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.
Search GitHub for public proof-of-concept (PoC) exploit repositories for a CVE. Results are sorted by star count to surface the most credible exploits first. Args: cve_id: CVE identifier (e.g. CVE-2021-44228). 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 check_exploit_availability: 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.
check_exploit_availability 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 check_exploit_availability 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 check_exploit_availability. 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.
check_exploit_availability 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.