AI agents use register-health-check to create or update resources in Consul MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Consul MCP Server environment.
This tool creates or registers a new health check, which is a write operation that modifies Consul's state. While reversible (the check can be deregistered via 'deregister-health-check'), it affects service health tracking and monitoring.
From the tool's definition Tool name 'register-health-check' and description 'Register a health check with Consul' indicate creation of a new health check configuration, a reversible modification to Consul's state.
Documented attack patterns abuse exactly the kind of access register-health-check 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 register-health-check:
{
"version": "1",
"default": "deny",
"tools": {
"register-health-check": {
"limits": [
{
"counter": "register-health-check_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}register-health-check 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.
Register a health check with Consul. It is categorised as a Write tool in the Consul MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Consul MCP Server MCP server in PolicyLayer and add a rule for register-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.
register-health-check 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 register-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.
Set action: deny in the PolicyLayer policy for register-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.
register-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.
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.