AI agents invoke metasploit_run to trigger actions in Kali Security MCP. 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 tool executes external operations (Metasploit modules) whose effects depend entirely on the module arguments chosen by the AI agent. Metasploit is a penetration testing framework containing hundreds of exploits and payloads. An AI agent could misuse this to execute malicious code, compromise systems, establish persistence, or cause widespread damage. The blast radius is critical in a real environment.
From the tool's definition Tool name 'metasploit_run' combined with description 'Execute a Metasploit module' indicates execution of arbitrary Metasploit payloads and exploits.
Documented attack patterns abuse exactly the kind of access metasploit_run gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali Security MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for metasploit_run:
{
"version": "1",
"default": "deny",
"tools": {
"metasploit_run": {
"limits": [
{
"counter": "metasploit_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}metasploit_run stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute a Metasploit module. It is categorised as a Execute tool in the Kali Security MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali Security 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 Kali Security MCP. 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 Kali Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 249 Kali Security MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
249 Kali Security MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.