add_bucket_to_project
Привязывает существующее S3-хранилище к проекту.
This record as markdown: /tools/timeweb-mcp/add-bucket-to-project.md
What add_bucket_to_project does on Timeweb
AI agents use add_bucket_to_project 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 |
|---|---|---|---|
project_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID проекта, куда добавить хранилище |
resource_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID хранилища |
Parameters from the server's own tool schema.
Why add_bucket_to_project is rated Medium
This tool creates an association between an S3 bucket and a project, which is a reversible write operation. It modifies project metadata/configuration without deleting data. The severity is medium because misconfiguration could expose storage access, but the operation itself is not destructive or financial.
From the tool's definition Tool name 'add_bucket_to_project' and description 'Привязывает существующее S3-хранилище к проекту' (Attaches an existing S3 storage to a project) indicate a create/link operation that modifies project configuration.
Attacks that exploit this kind of access
The rule that runs add_bucket_to_project 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_to_project, this is the rule to start with:
add_bucket_to_project 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_to_project call is checked against it from then on.
Questions about add_bucket_to_project
Привязывает существующее 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.
add_bucket_to_project accepts 2 parameters: project_id, resource_id. Required: project_id, resource_id. 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_to_project: 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_to_project 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_to_project 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_to_project. 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_to_project 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