This record as markdown: /tools/io-github-kivanccakmak-yaver/cloud-plans.md
What cloud_plans does on Yaver
AI agents call cloud_plans 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.
Why cloud_plans is rated Low
This tool performs a read-only query of cloud plan data. It retrieves and presents pricing and specifications to the user with no side effects, data modification, code execution, or destructive operations. The verb 'List' confirms it is a simple data retrieval operation.
From the tool's definition Tool name 'cloud_plans' and description 'List available Yaver Cloud plans with specs and pricing' indicate a retrieval operation that queries and displays pricing and plan information without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs cloud_plans 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_plans, this is the rule to start with:
cloud_plans 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_plans call is checked against it from then on.
Questions about cloud_plans
List available Yaver Cloud plans with specs and pricing. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for cloud_plans: 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_plans 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_plans 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_plans. 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_plans 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