Search for proof-of-concept exploits across GitHub, Exploit-DB, and Nuclei templates.
AI agents call check_poc_exists 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 read-only queries against public vulnerability databases and repositories to determine the existence of proof-of-concept code. It gathers intelligence about available exploits but does not execute code, modify data, delete data, or perform any irreversible actions.
From the tool's definition The tool 'check_poc_exists' searches for proof-of-concept exploits across public repositories (GitHub, Exploit-DB, Nuclei templates). The verb 'search' and 'check' indicate a query operation that retrieves information without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access check_poc_exists 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_poc_exists:
{
"version": "1",
"default": "deny",
"tools": {
"check_poc_exists": {}
}
}check_poc_exists 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 for proof-of-concept exploits across GitHub, Exploit-DB, and Nuclei templates. 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_poc_exists: 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_poc_exists 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_poc_exists 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_poc_exists. 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_poc_exists 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.