New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

cloud_scale

Change Yaver Cloud plan tier.

SERVERYaver SOURCEyaver-cli
Critical RISK CLASS
Category Financial
Parameters 11 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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

Questions about cloud_scale

What does the cloud_scale tool do? +

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.

What parameters does cloud_scale accept? +

cloud_scale accepts 1 parameter: plan. Required: plan. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on cloud_scale? +

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.

What risk level is cloud_scale? +

cloud_scale is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cloud_scale? +

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.

How do I block cloud_scale completely? +

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.

What MCP server provides cloud_scale? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.