AI agents call cloud_list_clickpipes 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 tool retrieves and enumerates ClickPipes (data pipeline configurations) for a given service. It performs a query operation that returns information without creating, modifying, deleting, or executing any changes. The blast radius of misuse is minimal—an attacker gains visibility into existing pipelines but cannot alter infrastructure or access underlying data beyond enumeration.
From the tool's definition Tool name 'cloud_list_clickpipes' uses the verb 'list', and the description states 'List all ClickPipes for a service' — both clearly indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access cloud_list_clickpipes 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_clickpipes:
{
"version": "1",
"default": "deny",
"tools": {
"cloud_list_clickpipes": {}
}
} cloud_list_clickpipes 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 ClickPipes for a service. 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_clickpipes: 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_clickpipes 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_clickpipes 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_clickpipes. 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_clickpipes 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.