AI agents invoke gophish_attack to trigger actions in Kali. 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 an external framework (GoPhish) that launches phishing campaigns. The effects are highly dependent on how the AI agent configures it (target domains, recipients, payloads), making it Execute rather than a fixed operation. The blast radius is critical because phishing attacks can compromise credentials, enable account takeovers, and facilitate broader system breaches.
From the tool's definition Tool name 'gophish_attack' and description 'Execute GoPhish phishing framework' indicate execution of a phishing attack framework. GoPhish is a legitimate phishing simulation tool but can be weaponized for unauthorized attacks.
Attacks that exploit this kind of access
Execute GoPhish phishing framework. It is categorised as a Execute tool in the Kali MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali MCP server in PolicyLayer and add a rule for gophish_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. Nothing to install.
gophish_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 gophish_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 gophish_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.
gophish_attack is provided by the Kali MCP server (pentestt00ls/kali-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 →