phone_project_runtime_deploy

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 91 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/phone-project-runtime-deploy.md

WHAT IT DOES

What phone_project_runtime_deploy does on Yaver

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.

RISK

Why phone_project_runtime_deploy is rated High

This tool executes deployment operations that trigger real infrastructure changes across multiple cloud providers and deployment targets. While not destructive (deployments are typically reversible), it clearly performs external operations whose effects depend on user-provided arguments. It is more severe than Write since it deploys code to production-like environments.

From the tool's definition Tool description states it can "deploy for a phone sandbox", "promote to Convex Cloud or Cloudflare Workers", "push to Yaver Cloud or a custom/self-hosted Yaver target".

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs phone_project_runtime_deploy 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 phone_project_runtime_deploy, this is the rule to start with:

phone_project_runtime_deploy Rate-limited

phone_project_runtime_deploy 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "phone_project_runtime_deploy": {
      "limits": [
        {
          "counter": "phone_project_runtime_deploy_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every phone_project_runtime_deploy call is checked against it from then on.

FAQ

Questions about phone_project_runtime_deploy

What does the phone_project_runtime_deploy tool do? +

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.

What parameters does phone_project_runtime_deploy accept? +

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.

How do I enforce a policy on phone_project_runtime_deploy? +

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.

What risk level is phone_project_runtime_deploy? +

phone_project_runtime_deploy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit phone_project_runtime_deploy? +

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.

How do I block phone_project_runtime_deploy completely? +

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.

What MCP server provides phone_project_runtime_deploy? +

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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → High-risk tools on this server →

Across the catalogue

deploy_git_repo on cPanel MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →