phone_project_promote
Plan (and optionally run) a switch-engine migration from a phone project to any of the 19 switch targets (sqlite-local, sqlite-turso, postgres-local, postgres-neon, supabase-cloud, convex-cloud, etc.). Same 7-day rollback window as a regular switch.
This record as markdown: /tools/io-github-kivanccakmak-yaver/phone-project-promote.md
What phone_project_promote does on Yaver
AI agents invoke phone_project_promote 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 | |
target | string | Yes | |
dry_run | boolean | — |
Parameters from the server's own tool schema.
Why phone_project_promote is rated High
When run (not just planned), this tool triggers a significant infrastructure migration that changes the underlying database engine for a project. While a 7-day rollback window exists (making it not fully irreversible), the execution of a live migration with potential data movement and schema changes across backends qualifies as Execute rather than Write due to the complexity and external system impact.
From the tool's definition 'Plan (and optionally run) a switch-engine migration' and 'switch targets (sqlite-local, sqlite-turso, postgres-local, postgres-neon, supabase-cloud, convex-cloud, etc.)' — the tool can actively execute a database engine migration across 19 possible backends
Attacks that exploit this kind of access
The rule that runs phone_project_promote 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_promote, this is the rule to start with:
phone_project_promote 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 phone_project_promote call is checked against it from then on.
Questions about phone_project_promote
Plan (and optionally run) a switch-engine migration from a phone project to any of the 19 switch targets (sqlite-local, sqlite-turso, postgres-local, postgres-neon, supabase-cloud, convex-cloud, etc.). Same 7-day rollback window as a regular switch. 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_promote accepts 4 parameters: run, slug, target, dry_run. Required: slug, target. 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_promote: 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_promote 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_promote 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_promote. 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_promote 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