Perform password spraying attacks across multiple targets with configurable options.
AI agents invoke nxc_spray to trigger actions in Sec Netexec. 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.
Password spraying is an executable attack that performs credential testing against network targets. While it doesn't directly delete or move money, it actively exercises external systems in ways that can cause operational harm (account lockouts, IDS alerts, security incidents).
From the tool's definition Tool enables 'password spraying attacks across multiple targets' — an active offensive operation that attempts unauthorized authentication, triggering external security systems and potentially locking accounts or triggering alerts.
Attacks that exploit this kind of access
Perform password spraying attacks across multiple targets with configurable options. It is categorised as a Execute tool in the Sec Netexec MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sec Netexec MCP server in PolicyLayer and add a rule for nxc_spray: 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 Sec Netexec. Nothing to install.
nxc_spray 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 nxc_spray 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 nxc_spray. 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.
nxc_spray is provided by the Sec Netexec MCP server (schwarztim/sec-netexec-mcp). 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 →