search_shellcodes
AI agents call search_shellcodes 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 retrieves shellcode data from a security research database. It has no side effects—it queries existing information without modifying, deleting, or executing code. The blast radius of misuse is low: an AI agent retrieving shellcode references poses less risk than execution of those payloads.
From the tool's definition Tool name 'search_shellcodes' and server context indicate data retrieval from Exploit-DB database. The server description emphasizes 'searching for exploits, shellcodes' and 'retrieve technical security data', with sibling tools like 'search_exploits' and…
Attacks that exploit this kind of access
search_shellcodes. 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 search_shellcodes: 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.
search_shellcodes 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 search_shellcodes 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 search_shellcodes. 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.
search_shellcodes 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 →