update_database_cluster

Изменяет параметры кластера базы данных: название, тариф, описание, публичную сеть (PATCH /api/v1/databases/{db_cluster_id}).

SERVERTimeweb SOURCEtimeweb-mcp

Medium RISK CLASS

Category Write

Parameters 51 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/timeweb-mcp/update-database-cluster.md

WHAT IT DOES

What update_database_cluster does on Timeweb

AI agents use update_database_cluster to create or update resources in Timeweb, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Timeweb environment.

Parameter	Type	Required	Description
`name`	string	—	НЕ ОБЯЗАТЕЛЬНОЕ ПОЛЕ - новое название кластера
`preset_id`	integer	—	НЕ ОБЯЗАТЕЛЬНОЕ ПОЛЕ - новый ID тарифа
`description`	string	—	НЕ ОБЯЗАТЕЛЬНОЕ ПОЛЕ - описание кластера
`db_cluster_id`	integer	Yes	ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID кластера базы данных
`is_enabled_public_network`	boolean	—	НЕ ОБЯЗАТЕЛЬНОЕ ПОЛЕ - включить/выключить публичный IP

Parameters from the server's own tool schema.

RISK

Why update_database_cluster is rated Medium

This tool modifies database cluster configuration reversibly via PATCH. It changes parameters (name, tariff, description, network settings) but does not delete or destroy data/resources. Tariff changes could have financial implications, but the primary action is configuration modification rather than payment processing.

From the tool's definition Tool name 'update_database_cluster' and description 'Изменяет параметры кластера базы данных' (Changes database cluster parameters); performs PATCH operation on database cluster configuration including name, tariff, description, and public network settings.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_database_cluster safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Timeweb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_database_cluster, this is the rule to start with:

update_database_cluster Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Timeweb, apply this rule, and every update_database_cluster call is checked against it from then on.

FAQ

Questions about update_database_cluster

What does the update_database_cluster tool do? +

Изменяет параметры кластера базы данных: название, тариф, описание, публичную сеть (PATCH /api/v1/databases/{db_cluster_id}). It is categorised as a Write tool in the Timeweb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_database_cluster accept? +

update_database_cluster accepts 5 parameters: name, preset_id, description, db_cluster_id, is_enabled_public_network. Required: db_cluster_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_database_cluster? +

Register the Timeweb MCP server in PolicyLayer and add a rule for update_database_cluster: 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 Timeweb. Nothing to install.

What risk level is update_database_cluster? +

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

Can I rate-limit update_database_cluster? +

Yes. Add a rate_limit block to the update_database_cluster 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 update_database_cluster completely? +

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

update_database_cluster is provided by the Timeweb MCP server (timeweb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Timeweb, and thousands of servers like it.

This server

All 245 Timeweb tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →