phone_project_push
Export a local phone project and push it to another reachable Yaver agent via /phone/projects/receive. Use this for explicit promotion to your dev machine, your own cloud host, or Yaver Cloud. Local source project remains local unless you choose otherwise.
This record as markdown: /tools/io-github-kivanccakmak-yaver/phone-project-push.md
What phone_project_push does on Yaver
AI agents use phone_project_push to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | |
skip_seed | boolean | — | |
on_conflict | string | — | reject | rename | overwrite |
target_slug | string | — | Optional slug override on the target |
containerize | boolean | — | Include Docker scaffold in the exported bundle before pushing |
include_data | boolean | — | Include local.db so runtime rows survive promotion |
target_base_url | string | Yes | Remote Yaver agent base URL, e.g. https://cloud.yaver.io or https://relay.yaver.io/d/<device> |
target_auth_token | string | — | Optional bearer token for the target. Defaults to local config auth token, then the current agent token if available. |
Parameters from the server's own tool schema.
Why phone_project_push is rated Medium
This tool creates or modifies state on remote systems by pushing/exporting project data to another Yaver agent. It is a Write operation because it transfers and potentially instantiates data on a target system, which is reversible and non-destructive.
From the tool's definition Tool description states it will 'Export a local phone project and push it to another reachable Yaver agent' and explicitly mentions 'promotion' across environments.
Attacks that exploit this kind of access
The rule that runs phone_project_push 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_push, this is the rule to start with:
phone_project_push stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_push call is checked against it from then on.
Questions about phone_project_push
Export a local phone project and push it to another reachable Yaver agent via /phone/projects/receive. Use this for explicit promotion to your dev machine, your own cloud host, or Yaver Cloud. Local source project remains local unless you choose otherwise. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
phone_project_push accepts 8 parameters: slug, skip_seed, on_conflict, target_slug, containerize, include_data, target_base_url, target_auth_token. Required: slug, target_base_url. 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_push: 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_push is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the phone_project_push 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_push. 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_push 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