This record as markdown: /tools/io-github-kivanccakmak-yaver/cloud-redeploy.md
What cloud_redeploy does on Yaver
AI agents invoke cloud_redeploy 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.
Why cloud_redeploy is rated High
This tool executes an external deployment operation that rebuilds and redeploys an application. While it can be re-run (not strictly irreversible), it triggers significant external operations affecting live environments, making it Execute with high severity due to the blast radius of pushing to production.
From the tool's definition "Rebuild and redeploy from latest code" — triggers a build and deployment pipeline operation
Attacks that exploit this kind of access
The rule that runs cloud_redeploy 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_redeploy, this is the rule to start with:
cloud_redeploy 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 cloud_redeploy call is checked against it from then on.
Questions about cloud_redeploy
Rebuild and redeploy from latest code. 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.
Register the Yaver MCP server in PolicyLayer and add a rule for cloud_redeploy: 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_redeploy 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 cloud_redeploy 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_redeploy. 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_redeploy 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