AI agents call list-events 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 and displays event data from Consul without creating, modifying, deleting, or triggering actions. It is a passive read operation with minimal blast radius if misused by an AI agent—the worst outcome would be information disclosure about historical events.
From the tool's definition Tool name 'list-events' and description 'List all events' indicate a query/retrieval operation with no modification, deletion, or execution of external systems.
Documented attack patterns abuse exactly the kind of access list-events 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 list-events:
{
"version": "1",
"default": "deny",
"tools": {
"list-events": {}
}
}list-events 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.
List all events. 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 list-events: 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.
list-events 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 list-events 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 list-events. 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.
list-events 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.