AI agents call search_modules to retrieve information from MSFConsole MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'search_modules' clearly indicates a retrieval operation that queries available Metasploit modules. While the empty description prevents full certainty, the naming convention and context of a penetration testing framework strongly suggest this is a search/query function rather than an execution or modification tool.
From the tool's definition Tool name 'search_modules' indicates a query/search operation with no destructive side effects. Sibling tools include 'module_operations', 'payload_generation', 'execute_msf_command', and 'session_management', suggesting this tool is a read-only search…
Documented attack patterns abuse exactly the kind of access search_modules gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MSFConsole MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_modules:
{
"version": "1",
"default": "deny",
"tools": {
"search_modules": {}
}
}search_modules 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_modules. It is categorised as a Read tool in the MSFConsole MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MSFConsole MCP Server MCP server in PolicyLayer and add a rule for search_modules: 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 MSFConsole MCP Server. Nothing to install.
search_modules 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_modules 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_modules. 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_modules is provided by the MSFConsole MCP Server MCP server (lyftium-inc/msfconsole-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MSFConsole 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.
9 MSFConsole MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.