list_bucket_users
Возвращает всех пользователей-администраторов S3-хранилищ аккаунта: id и access_key. secret_key может быть в ответе, но на практике его безопаснее обновлять через update_bucket_user.
This record as markdown: /tools/timeweb-mcp/list-bucket-users.md
What list_bucket_users does on Timeweb
AI agents call list_bucket_users to retrieve information from Timeweb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_bucket_users is rated Low
This tool retrieves credential information (user IDs and access keys) for S3 storage administrators. While it is a read operation with no side effects, the severity is high because it exposes sensitive authentication credentials that could be used to compromise cloud storage if leaked. The potential blast radius includes unauthorized access to all S3 buckets if credentials are misused by an AI agent.
From the tool's definition Tool name 'list_bucket_users' and description states it 'Возвращает всех пользователей' (returns all users) with their id and access_key. The verb 'list/returns' indicates data retrieval with no modification.
Attacks that exploit this kind of access
The rule that runs list_bucket_users 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 list_bucket_users, this is the rule to start with:
list_bucket_users is read-only, so it stays allowed. 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 list_bucket_users call is checked against it from then on.
Questions about list_bucket_users
Возвращает всех пользователей-администраторов S3-хранилищ аккаунта: id и access_key. secret_key может быть в ответе, но на практике его безопаснее обновлять через update_bucket_user. It is categorised as a Read tool in the Timeweb MCP Server, which means it retrieves data without modifying state.
Register the Timeweb MCP server in PolicyLayer and add a rule for list_bucket_users: 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.
list_bucket_users is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_bucket_users 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 list_bucket_users. 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.
list_bucket_users 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