High-level runtime deploy for a phone sandbox. Can connect provider accounts, promote to Convex Cloud or Cloudflare Workers, push to Yaver Cloud or a custom/self-hosted Yaver target, or do several of those in one call.
AI agents invoke phone_project_runtime_deploy 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 |
|---|---|---|---|
run | boolean | — | |
slug | string | Yes | |
dry_run | boolean | — | |
targets | array | — | Any of: convex-cloud, cloudflare-workers, yaver-cloud, self-hosted, custom |
providers | array | — | Optional provider account writes. Each item: {provider,label,fields} |
containerize | boolean | — | |
include_data | boolean | — | |
target_base_url | string | — | Required when targets includes custom unless YAVER_SELF_HOSTED_BASE_URL is configured |
target_auth_token | string | — | Optional bearer token for yaver-cloud/custom push target |
Parameters from the server's own tool schema.
phone_project_runtime_deploy triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
High-level runtime deploy for a phone sandbox. Can connect provider accounts, promote to Convex Cloud or Cloudflare Workers, push to Yaver Cloud or a custom/self-hosted Yaver target, or do several of those in one call. 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.
phone_project_runtime_deploy accepts 9 parameters: run, slug, dry_run, targets, providers, containerize, include_data, target_base_url, target_auth_token. Required: slug. 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 phone_project_runtime_deploy: 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.
phone_project_runtime_deploy 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 phone_project_runtime_deploy 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 phone_project_runtime_deploy. 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.
phone_project_runtime_deploy 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.