remote_provision
Spin up a new VPS from phone. Supports Hetzner and DigitalOcean.
This record as markdown: /tools/io-github-kivanccakmak-yaver/remote-provision.md
What remote_provision does on Yaver
AI agents invoke remote_provision to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
size | string | Yes | |
region | string | — | Region (default: closest) |
provider | string | Yes |
Parameters from the server's own tool schema.
Why remote_provision is rated High
This tool provisions cloud infrastructure (VPS) on external providers (Hetzner, DigitalOcean), triggering external operations with real-world consequences. While it may have financial implications (paid VPS instances), the primary action is executing an infrastructure provisioning operation rather than directly moving money.
From the tool's definition Spin up a new VPS from phone. Supports Hetzner and DigitalOcean.
Attacks that exploit this kind of access
The rule that runs remote_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 remote_provision, this is the rule to start with:
remote_provision stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 remote_provision call is checked against it from then on.
Questions about remote_provision
Spin up a new VPS from phone. Supports Hetzner and DigitalOcean. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
remote_provision accepts 3 parameters: size, region, provider. Required: size, provider. 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 remote_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.
remote_provision is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the remote_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 remote_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.
remote_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.
Across the catalogue