security.exploit-availability
Does public exploit code exist for a CVE, and where? Pass cve (CVE-2021-44228). Returns hasPublicExploit, count, hasMetasploitModule + hasVerifiedExploit flags, and Exploit-DB entries (description, type, platform, date, link). Bundled Exploit-DB index (~25k CVEs). The
This record as markdown: /tools/io-github-2s-io-mcp/security.exploit-availability.md
What security.exploit-availability does on Mcp
AI agents call security.exploit-availability to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why security.exploit-availability is rated Low
This tool performs a lookup/search operation against a bundled Exploit-DB index to retrieve factual information about exploit availability. It has no side effects, does not execute code, and does not modify any data. While the information returned could be used maliciously by an agent, the tool itself is purely informational (Read category).
From the tool's definition Tool queries and retrieves information about public exploits for CVEs: 'Does public exploit code exist for a CVE, and where?' Returns data fields (hasPublicExploit, count, hasMetasploitModule flags, Exploit-DB entries).
Attacks that exploit this kind of access
The rule that runs security.exploit-availability safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For security.exploit-availability, this is the rule to start with:
security.exploit-availability 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 Mcp, apply this rule, and every security.exploit-availability call is checked against it from then on.
Questions about security.exploit-availability
Does public exploit code exist for a CVE, and where? Pass cve (CVE-2021-44228). Returns hasPublicExploit, count, hasMetasploitModule + hasVerifiedExploit flags, and Exploit-DB entries (description, type, platform, date, link). Bundled Exploit-DB index (~25k CVEs). The. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for security.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 Mcp. Nothing to install.
security.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 security.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 security.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.
security.exploit-availability is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue