cloud_provision
Provision a resource on a cloud provider using stored credentials. Hosts: neon, supabase-cloud, turso, cloudflare-d1, vercel, hetzner, railway.
This record as markdown: /tools/io-github-kivanccakmak-yaver/cloud-provision.md
What cloud_provision does on Yaver
AI agents call cloud_provision to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
host | string | Yes | |
name | string | Yes | |
opts | string | — | JSON options |
Parameters from the server's own tool schema.
Why cloud_provision is rated Low
Even though cloud_provision only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts URL/endpoint input (host)
Attacks that exploit this kind of access
The rule that runs cloud_provision 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 cloud_provision, this is the rule to start with:
cloud_provision 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 Yaver, apply this rule, and every cloud_provision call is checked against it from then on.
Questions about cloud_provision
Provision a resource on a cloud provider using stored credentials. Hosts: neon, supabase-cloud, turso, cloudflare-d1, vercel, hetzner, railway. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
cloud_provision accepts 3 parameters: host, name, opts. Required: host, 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 cloud_provision: 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.
cloud_provision 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 cloud_provision 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 cloud_provision. 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.
cloud_provision 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