yersinia_attack
A execute tool on the Kali Security MCP server.
This record as markdown: /tools/seac-25-kali-security-mcp/yersinia-attack.md
What yersinia_attack does on Kali Security MCP
AI agents invoke yersinia_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.
Why yersinia_attack is rated High
Yersinia is used to launch network attacks against Layer 2 protocols, which can disrupt network infrastructure (e.g., DHCP starvation, STP root bridge takeover). While the description is empty, the tool name combined with the server's explicit 'attack' and penetration testing context strongly implies active exploitation/attack execution. The blast radius is critical as misuse could disrupt entire network segments.
From the tool's definition Tool name 'yersinia_attack' — Yersinia is a well-known Kali Linux network protocol attack tool targeting Layer 2 protocols (STP, CDP, DHCP, etc.). Server context explicitly describes penetration testing and attack workflows.
Attacks that exploit this kind of access
The rule that runs yersinia_attack safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kali Security MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For yersinia_attack, this is the rule to start with:
yersinia_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Kali Security MCP, apply this rule, and every yersinia_attack call is checked against it from then on.
Questions about yersinia_attack
yersinia_attack is a execute tool on the Kali Security MCP server. 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 yersinia_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.
yersinia_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 yersinia_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 yersinia_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.
yersinia_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.
More on Kali Security, and thousands of servers like it.
Across the catalogue