AI agents call cloud_list_members to retrieve information from MCP ClickHouse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that retrieves membership information. It has no side effects, does not modify data, and does not execute external operations. While it exposes organizational structure information, the blast radius is limited to information disclosure, making it low severity.
From the tool's definition Tool name 'cloud_list_members' and description 'List all members in an organization' clearly indicate a retrieval operation that queries organizational membership data without modifying, deleting, or executing any operations.
Documented attack patterns abuse exactly the kind of access cloud_list_members gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP ClickHouse, and nothing reaches the server without passing your rules. This is the rule we recommend for cloud_list_members:
{
"version": "1",
"default": "deny",
"tools": {
"cloud_list_members": {}
}
}cloud_list_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.
List all members in an organization. It is categorised as a Read tool in the MCP ClickHouse MCP Server, which means it retrieves data without modifying state.
Register the MCP ClickHouse MCP server in PolicyLayer and add a rule for cloud_list_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 MCP ClickHouse. Nothing to install.
cloud_list_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 cloud_list_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 cloud_list_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.
cloud_list_members is provided by the MCP ClickHouse MCP server (oualib/chmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP ClickHouse, 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.
55 MCP ClickHouse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.