add_bucket_subdomains
Добавляет один или несколько поддоменов к S3-хранилищу. Для каждого возвращает статус: success, empty_cname (нет CNAME-записи), duplicate или failed. После добавления выпускай SSL через add_bucket_subdomain_certificate.
This record as markdown: /tools/timeweb-mcp/add-bucket-subdomains.md
What add_bucket_subdomains does on Timeweb
AI agents use add_bucket_subdomains 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 |
|---|---|---|---|
bucket_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID S3-хранилища |
subdomains | array | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - массив поддоменов для добавления, например ['test.example.com'] |
Parameters from the server's own tool schema.
Why add_bucket_subdomains is rated Medium
An AI agent can call add_bucket_subdomains faster than any human can review: one bad instruction and it creates or modifies resources in Timeweb by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs add_bucket_subdomains 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 add_bucket_subdomains, this is the rule to start with:
add_bucket_subdomains 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Timeweb, apply this rule, and every add_bucket_subdomains call is checked against it from then on.
Questions about add_bucket_subdomains
Добавляет один или несколько поддоменов к S3-хранилищу. Для каждого возвращает статус: success, empty_cname (нет CNAME-записи), duplicate или failed. После добавления выпускай SSL через add_bucket_subdomain_certificate. 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.
add_bucket_subdomains accepts 2 parameters: bucket_id, subdomains. Required: bucket_id, subdomains. 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 add_bucket_subdomains: 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.
add_bucket_subdomains 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 add_bucket_subdomains 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 add_bucket_subdomains. 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.
add_bucket_subdomains 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.
This server
Across the catalogue