This record as markdown: /tools/io-github-kivanccakmak-yaver/cloud-scale.md
What cloud_scale does on Yaver
AI agents use cloud_scale to commit financial operations through Yaver, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
plan | string | Yes |
Parameters from the server's own tool schema.
Why cloud_scale is rated Critical
Changing a cloud plan tier directly commits to a different subscription level, which constitutes a financial obligation. Upgrading to a higher tier would incur additional charges, making this a Financial category action. The blast radius is high because an AI agent could silently upgrade to a more expensive plan tier without user awareness.
From the tool's definition Change Yaver Cloud plan tier
Attacks that exploit this kind of access
The rule that runs cloud_scale 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_scale, this is the rule to start with:
Any call to cloud_scale is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every cloud_scale call is checked against it from then on.
Questions about cloud_scale
Change Yaver Cloud plan tier. It is categorised as a Financial tool in the Yaver MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
cloud_scale accepts 1 parameter: plan. Required: plan. 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_scale: 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_scale is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cloud_scale 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_scale. 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_scale 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