cloud_update_backup_configuration

THE RISK

Medium Risk

Why cloud_update_backup_configuration needs a policy

This tool modifies backup configuration settings in ClickHouse Cloud infrastructure. While the changes are reversible (Write rather than Destructive), incorrect backup configuration could disable data protection, leading to high blast radius if an agent misconfigures backups accidentally. Severity is high due to potential operational impact on data safety mechanisms.

From the tool's definition Tool name 'cloud_update_backup_configuration' indicates modification of backup settings. The description is empty, but the verb 'update' and context of backup configuration management on ClickHouse Cloud (alongside other create/delete operations) confirm this…

Documented attack patterns abuse exactly the kind of access cloud_update_backup_configuration gives an agent:

POLICY

How to control cloud_update_backup_configuration

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_update_backup_configuration:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cloud_update_backup_configuration": {
      "limits": [
        {
          "counter": "cloud_update_backup_configuration_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

cloud_update_backup_configuration 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.

Create a free account and register MCP ClickHouse — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP ClickHouse tools

Destructive cloud_delete_api_key Delete an API key. Destructive cloud_delete_clickpipe Delete a ClickPipe. Destructive cloud_delete_invitation Delete/cancel an invitation. Destructive cloud_delete_query_endpoint_config Delete query endpoint configuration for a service (experimental). Destructive cloud_delete_reverse_private_endpoint Delete a reverse private endpoint (beta). Destructive cloud_delete_service Delete a service (must be stopped first). Destructive cloud_remove_member Remove a member from the organization. Execute run_query Run a query in a ClickHouse database.

All 55 MCP ClickHouse tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cloud_update_backup_configuration

What does the cloud_update_backup_configuration tool do? +

cloud_update_backup_configuration. 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.

How do I enforce a policy on cloud_update_backup_configuration? +

Register the MCP ClickHouse MCP server in PolicyLayer and add a rule for cloud_update_backup_configuration: 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.

What risk level is cloud_update_backup_configuration? +

cloud_update_backup_configuration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cloud_update_backup_configuration? +

Yes. Add a rate_limit block to the cloud_update_backup_configuration 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.

How do I block cloud_update_backup_configuration completely? +

Set action: deny in the PolicyLayer policy for cloud_update_backup_configuration. 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.

What MCP server provides cloud_update_backup_configuration? +

cloud_update_backup_configuration 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.

Enforce policy on every MCP ClickHouse tool call.

Start from MCP ClickHouse, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →