This record as markdown: /tools/io-github-kivanccakmak-yaver/storage-bucket-create.md
What storage_bucket_create does on Yaver
AI agents use storage_bucket_create to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Bucket name |
Parameters from the server's own tool schema.
Why storage_bucket_create is rated Medium
Creating an S3 bucket is a Write operation—it creates a new persistent resource in cloud storage that persists until explicitly deleted. While the action itself is reversible (the bucket can be deleted), it commits cloud infrastructure changes and incurs potential costs.
From the tool's definition Tool name 'storage_bucket_create' and description 'Create an S3 bucket' indicate irreversible creation of cloud infrastructure resource.
Attacks that exploit this kind of access
The rule that runs storage_bucket_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For storage_bucket_create, this is the rule to start with:
storage_bucket_create 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 Yaver, apply this rule, and every storage_bucket_create call is checked against it from then on.
Questions about storage_bucket_create
Create an S3 bucket. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
storage_bucket_create accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for storage_bucket_create: 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 Yaver. Nothing to install.
storage_bucket_create 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 storage_bucket_create 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 storage_bucket_create. 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.
storage_bucket_create is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue