AI agents use save_attack_preset to create or update resources in Hashcat MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hashcat MCP Server environment.
This is a Write operation because it creates or stores configuration data (a preset) that can be reused later. It is reversible—presets can be deleted or overwritten. While it supports hashcracking activities (a security assessment context), the tool itself only manages configuration metadata, not executing attacks or destroying data.
From the tool's definition The tool 'save_attack_preset' saves (creates/stores) attack configuration data as a preset for reuse. The verb 'save' indicates data creation or modification in persistent storage.
Documented attack patterns abuse exactly the kind of access save_attack_preset gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Hashcat MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for save_attack_preset:
{
"version": "1",
"default": "deny",
"tools": {
"save_attack_preset": {
"limits": [
{
"counter": "save_attack_preset_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} save_attack_preset stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Save attack configuration as preset. It is categorised as a Write tool in the Hashcat MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hashcat MCP Server MCP server in PolicyLayer and add a rule for save_attack_preset: 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 Hashcat MCP Server. Nothing to install.
save_attack_preset is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_attack_preset 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 save_attack_preset. 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.
save_attack_preset is provided by the Hashcat MCP Server MCP server (mordavid/hashcat-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Hashcat MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 Hashcat MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.