Get statistics about the exploit database
AI agents call get_database_stats to retrieve information from Exploit-DB 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 operation to retrieve statistical information (counts, metrics, summaries) about the Exploit-DB database. It has no side effects, does not execute code, does not modify data, and does not retrieve actual exploit payloads or shellcode—it only returns informational statistics. The blast radius of misuse is negligible: an attacker cannot weaponize statistics alone.
From the tool's definition Tool name 'get_database_stats' and description 'Get statistics about the exploit database' indicate a query operation that retrieves aggregate metadata about the database without modifying, executing, or accessing sensitive exploit code itself.
Attacks that exploit this kind of access
Get statistics about the exploit database. It is categorised as a Read tool in the Exploit-DB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Exploit-DB MCP Server MCP server in PolicyLayer and add a rule for get_database_stats: 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 Exploit-DB MCP Server. Nothing to install.
get_database_stats 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 get_database_stats 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 get_database_stats. 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.
get_database_stats is provided by the Exploit-DB MCP Server MCP server (johnohhh1/exploitdb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →