Execute a Metasploit module.
AI agents invoke metasploit_run to trigger actions in MCP Kali Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This is Execute rather than Destructive because the tool itself triggers code execution but does not inherently delete or irreversibly destroy data—the destructive outcome depends on which specific Metasploit module an agent chooses to run. However, severity is high because Metasploit modules commonly result in system compromise, data exfiltration, lateral movement, and permanent system changes.
From the tool's definition Tool executes Metasploit modules, which are code-execution engines used to run exploit payloads, post-exploitation scripts, and arbitrary commands on target systems.
Attacks that exploit this kind of access
Execute a Metasploit module. It is categorised as a Execute tool in the MCP Kali Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Kali Server MCP server in PolicyLayer and add a rule for metasploit_run: 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 Kali Server. Nothing to install.
metasploit_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the metasploit_run 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 metasploit_run. 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.
metasploit_run is provided by the MCP Kali Server MCP server (wh0am123/mcp-kali-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.