AI agents call hermes_reset to permanently remove resources in Hermes — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Reset operations typically irreversibly clear system state, configurations, or task history. Without documentation, the scope of what gets reset is unknown, which increases risk. The tool could wipe agent state, task queues, or settings that were not trivial to establish.
From the tool's definition Tool name 'hermes_reset' with empty description suggests a reset operation. Combined with sibling tools (hermes_ask, hermes_cancel, hermes_check) that manage agent tasks, a reset likely clears state, configurations, or persistent operations—actions that…
Documented attack patterns abuse exactly the kind of access hermes_reset gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Hermes, and nothing reaches the server without passing your rules. This is the rule we recommend for hermes_reset:
{
"version": "1",
"default": "deny",
"hide": [
"hermes_reset"
]
}hermes_reset disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
hermes_reset. It is categorised as a Destructive tool in the Hermes MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hermes MCP server in PolicyLayer and add a rule for hermes_reset: 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 Hermes. Nothing to install.
hermes_reset is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the hermes_reset 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 hermes_reset. 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.
hermes_reset is provided by the Hermes MCP server (mlennie/hermes-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Hermes, 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.
4 Hermes tools catalogued and risk-classified — across an index of 43,000+ MCP servers.