deregister-health-check

THE RISK

Critical Risk

Why deregister-health-check needs a policy

Deregistering a health check permanently removes it from Consul's registry. This cannot be undone without re-registering the check, and removing a health check can cause services to appear healthy when they are not, potentially leading to traffic being routed to unhealthy instances. This qualifies as Destructive due to the irreversible nature of the removal and the high blast radius in a service mesh environment.

From the tool's definition 'Deregister a health check from Consul' — deregistration is an irreversible removal operation

Documented attack patterns abuse exactly the kind of access deregister-health-check gives an agent:

POLICY

How to control deregister-health-check

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 deregister-health-check:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "deregister-health-check"
  ]
}

deregister-health-check disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Consul MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Consul MCP Server tools

Destructive delete-kv Delete a key from the KV store Destructive destroy-session Destroy a session in Consul Destructive deregister-service Deregister a service from Consul Execute execute-prepared-query Execute a prepared query Execute fire-event Fire a new event Execute reload-agent Reload agent configuration Write create-prepared-query Create a new prepared query Write put-kv Put a value in the KV store

All 25 Consul MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Consul MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about deregister-health-check

What does the deregister-health-check tool do? +

Deregister a health check from 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.

How do I enforce a policy on deregister-health-check? +

Register the Consul MCP Server MCP server in PolicyLayer and add a rule for deregister-health-check: 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.

What risk level is deregister-health-check? +

deregister-health-check is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit deregister-health-check? +

Yes. Add a rate_limit block to the deregister-health-check 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 deregister-health-check completely? +

Set action: deny in the PolicyLayer policy for deregister-health-check. 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 deregister-health-check? +

deregister-health-check 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.

Enforce policy on every Consul MCP Server tool call.

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.

CHECK YOUR STACK →