AI agents use cloud_create_service to create or update resources in MCP ClickHouse — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP ClickHouse environment.
The tool creates a cloud service, which is a reversible Write operation that establishes infrastructure resources. While the description is empty (lowering confidence slightly), the name and context clearly indicate resource creation rather than read-only access, code execution, or destructive operations. This could incur costs or create persistent infrastructure, warranting high severity.
From the tool's definition Tool name 'cloud_create_service' indicates creation of a cloud service resource. Sibling tools show patterns of cloud infrastructure management including creation and deletion operations (cloud_create_api_key, cloud_create_clickpipe, cloud_delete_api_key, etc.
Documented attack patterns abuse exactly the kind of access cloud_create_service 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_create_service:
{
"version": "1",
"default": "deny",
"tools": {
"cloud_create_service": {
"limits": [
{
"counter": "cloud_create_service_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}cloud_create_service stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
cloud_create_service. It is categorised as a Write tool in the MCP ClickHouse MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP ClickHouse MCP server in PolicyLayer and add a rule for cloud_create_service: 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_create_service is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the cloud_create_service 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_create_service. 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_create_service 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.