eaphammer
A execute tool on the Nyxstrike MCP server.
This record as markdown: /tools/nyxstrike/eaphammer.md
What eaphammer does on Nyxstrike
AI agents invoke eaphammer to trigger actions in Nyxstrike. 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 eaphammer is rated High
EAPHammer is a publicly known offensive security tool used to conduct evil twin Wi-Fi attacks, steal RADIUS credentials, and perform man-in-the-middle attacks on WPA2-Enterprise networks.
From the tool's definition Tool name 'eaphammer' on a penetration testing platform; sibling tools include aircrack_ng, airbase_ng, advanced_payload_generation, ai_generate_attack_suite — all offensive security/wireless attack tools.
Attacks that exploit this kind of access
The rule that runs eaphammer safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nyxstrike, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For eaphammer, this is the rule to start with:
eaphammer 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 Nyxstrike, apply this rule, and every eaphammer call is checked against it from then on.
Questions about eaphammer
eaphammer is a execute tool on the Nyxstrike MCP server. It is categorised as a Execute tool in the Nyxstrike MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nyxstrike MCP server in PolicyLayer and add a rule for eaphammer: 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 Nyxstrike. Nothing to install.
eaphammer 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 eaphammer 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 eaphammer. 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.
eaphammer is provided by the Nyxstrike MCP server (CommonHuman-Lab/nyxstrike). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nyxstrike, and thousands of servers like it.
Across the catalogue