check_consul
Check Consul agent health and cluster leader. Returns agent node name, datacenter, server/client role, leader address, and Consul version. host: IP or hostname. port: default 8500 (Consul HTTP API port).
This record as markdown: /tools/aaronckj-mcp-nettools/check-consul.md
What check_consul does on Mcp Nettools
AI agents call check_consul to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_consul is rated Low
check_consul retrieves diagnostic and status information from a Consul agent and cluster without triggering any side effects, state changes, or commands. However, the exposed information (leader address, cluster topology, datacenter details) could be valuable reconnaissance for an attacker mapping infrastructure, which elevates severity to medium despite being Read-category.
From the tool's definition Tool description states it 'Returns agent node name, datacenter, server/client role, leader address, and Consul version' — purely informational retrieval with no modification or execution of infrastructure changes.
Attacks that exploit this kind of access
The rule that runs check_consul safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_consul, this is the rule to start with:
check_consul is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_consul call is checked against it from then on.
Questions about check_consul
Check Consul agent health and cluster leader. Returns agent node name, datacenter, server/client role, leader address, and Consul version. host: IP or hostname. port: default 8500 (Consul HTTP API port). It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.
Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_consul: 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 Mcp Nettools. Nothing to install.
check_consul is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_consul 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 check_consul. 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.
check_consul is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Nettools, and thousands of servers like it.
This server
Across the catalogue