cme_spray

Perform password spraying attacks across multiple targets. Supports jitter and continues on success options.

Server CrackMapExec MCP Server schwarztim/sec-crackmapexec-mcp
Category Execute
Risk class High
Parameters 00 required

What cme_spray does on CrackMapExec MCP Server

AI agents invoke cme_spray to trigger actions in CrackMapExec MCP Server. 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 cme_spray needs a policy

Password spraying is an active attack that attempts to authenticate with multiple credentials across target systems. While it could be considered Write (modifying authentication state) or Destructive (potentially locking accounts), it is most accurately Execute because: (1) it runs a coordinated attack sequence whose effects depend on argument values (target list, passwords, timing), (2) the primary effect is…

From the tool's definition Tool description states it performs 'password spraying attacks across multiple targets' with options for jitter and continuing on success.

Questions about cme_spray

What does the cme_spray tool do? +

Perform password spraying attacks across multiple targets. Supports jitter and continues on success options. It is categorised as a Execute tool in the CrackMapExec MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cme_spray? +

Register the CrackMapExec MCP Server MCP server in PolicyLayer and add a rule for cme_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 CrackMapExec MCP Server. Nothing to install.

What risk level is cme_spray? +

cme_spray is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit cme_spray? +

Yes. Add a rate_limit block to the cme_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.

How do I block cme_spray completely? +

Set action: deny in the PolicyLayer policy for cme_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.

What MCP server provides cme_spray? +

cme_spray is provided by the CrackMapExec MCP Server MCP server (schwarztim/sec-crackmapexec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.