AI agents call destroy-session to permanently remove resources in Consul MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'destroy' verb combined with 'session' indicates this operation permanently removes a session object from Consul's state. Sessions in Consul are used for distributed locking and health-based resource management; destroying a session irreversibly terminates locks and leases it manages, potentially disrupting dependent services and client operations. This cannot be undone, making it Destructive rather than Write.
From the tool's definition Tool name 'destroy-session' and description 'Destroy a session in Consul' indicate irreversible deletion of a session resource.
Documented attack patterns abuse exactly the kind of access destroy-session gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Consul MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for destroy-session:
{
"version": "1",
"default": "deny",
"hide": [
"destroy-session"
]
}destroy-session 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.
Destroy a session in Consul. It is categorised as a Destructive tool in the Consul MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Consul MCP Server MCP server in PolicyLayer and add a rule for destroy-session: 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 Consul MCP Server. Nothing to install.
destroy-session 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 destroy-session 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 destroy-session. 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.
destroy-session is provided by the Consul MCP Server MCP server (kocierik/consul-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Consul 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.
25 Consul MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.