AI agents invoke medusa_attack 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.
Medusa is a well-known parallel brute-force authentication tool that actively attempts credential combinations against remote services (SSH, FTP, HTTP, etc.). This tool executes live network attacks against authentication systems, which constitutes active offensive execution with high blast radius — it can compromise remote accounts and services.
From the tool's definition medusa_attack — 'Medusa 执行口令验证测试' (execute password/credential verification testing using Medusa, a parallel brute-force login tool)
Documented attack patterns abuse exactly the kind of access medusa_attack 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 medusa_attack:
{
"version": "1",
"default": "deny",
"tools": {
"medusa_attack": {
"limits": [
{
"counter": "medusa_attack_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}medusa_attack 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.
使用 Medusa 执行口令验证测试。. 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 medusa_attack: 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.
medusa_attack 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 medusa_attack 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 medusa_attack. 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.
medusa_attack 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.