update_bucket_user
Меняет secret_key пользователя-администратора S3-хранилища. После смены пароля нужно обновить конфигурацию всех клиентов, подключающихся к хранилищу.
This record as markdown: /tools/timeweb-mcp/update-bucket-user.md
What update_bucket_user does on Timeweb
AI agents use update_bucket_user 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 |
|---|---|---|---|
user_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID пользователя S3-хранилища |
secret_key | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - новый secret_key (1-255 символов) |
Parameters from the server's own tool schema.
Why update_bucket_user is rated Medium
An AI agent can call update_bucket_user 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 update_bucket_user 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_bucket_user, this is the rule to start with:
update_bucket_user 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 update_bucket_user call is checked against it from then on.
Questions about update_bucket_user
Меняет secret_key пользователя-администратора S3-хранилища. После смены пароля нужно обновить конфигурацию всех клиентов, подключающихся к хранилищу. 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.
update_bucket_user accepts 2 parameters: user_id, secret_key. Required: user_id, secret_key. 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 update_bucket_user: 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.
update_bucket_user 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 update_bucket_user 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 update_bucket_user. 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.
update_bucket_user 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