AI agents call get-agent-members to retrieve information from Consul MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about Consul agent members in the cluster. It performs a data query with no side effects, no state changes, and no external execution. This falls clearly into the Read category. Severity is low because exposing membership information is typically low-risk—it is often considered operational metadata rather than sensitive credentials or critical state.
From the tool's definition Tool name 'get-agent-members' and description 'Get agent members' indicate a query/retrieval operation. No modification, deletion, or execution of commands is implied. The action is read-only, consistent with Consul's agent member listing functionality.
Documented attack patterns abuse exactly the kind of access get-agent-members 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 get-agent-members:
{
"version": "1",
"default": "deny",
"tools": {
"get-agent-members": {}
}
}get-agent-members is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get agent members. It is categorised as a Read tool in the Consul MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Consul MCP Server MCP server in PolicyLayer and add a rule for get-agent-members: 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.
get-agent-members 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 get-agent-members 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 get-agent-members. 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.
get-agent-members 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.