install_k8s_addon
Устанавливает дополнение (addon) в кластер. Нужны тип, версия, config_type (basic/custom) и YAML-конфигурация. Каталог доступных дополнений — list_k8s_addon_configs.
This record as markdown: /tools/timeweb-mcp/install-k8s-addon.md
What install_k8s_addon does on Timeweb
AI agents invoke install_k8s_addon to trigger actions in Timeweb. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - тип дополнения (например, ingress, dbaas-operator) |
version | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - версия дополнения (например, 4.12.1) |
cluster_id | integer | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID кластера |
config_type | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - тип конфигурации: basic или custom |
yaml_config | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - YAML-конфигурация дополнения |
Parameters from the server's own tool schema.
Why install_k8s_addon is rated High
Installing an addon into a Kubernetes cluster is an execution/deployment action that modifies cluster runtime state. It runs/deploys software components into a live cluster, which can have significant blast radius (misconfigured addons can destabilize the cluster, expose services, or create security vulnerabilities). It goes beyond a simple write as it triggers external operations within the cluster environment.
From the tool's definition Устанавливает дополнение (addon) в кластер — installs an addon into a Kubernetes cluster, requiring type, version, config_type, and YAML configuration
Attacks that exploit this kind of access
The rule that runs install_k8s_addon 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 install_k8s_addon, this is the rule to start with:
install_k8s_addon stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Timeweb, apply this rule, and every install_k8s_addon call is checked against it from then on.
Questions about install_k8s_addon
Устанавливает дополнение (addon) в кластер. Нужны тип, версия, config_type (basic/custom) и YAML-конфигурация. Каталог доступных дополнений — list_k8s_addon_configs. It is categorised as a Execute tool in the Timeweb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
install_k8s_addon accepts 5 parameters: type, version, cluster_id, config_type, yaml_config. Required: type, version, cluster_id, config_type, yaml_config. The full parameter table on this page comes from the server's own tool schema.
Register the Timeweb MCP server in PolicyLayer and add a rule for install_k8s_addon: 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.
install_k8s_addon is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the install_k8s_addon 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 install_k8s_addon. 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.
install_k8s_addon 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.
More on Timeweb, and thousands of servers like it.
Across the catalogue