phone_project_export
Return a tgz of the project's portable manifest (schema + auth + seed + config + generated DDL). Base64-encoded so it round-trips through JSON. Supports include_data and containerize so MCP clients can export the exact same local-first backend bundle the mobile app and CLI use.
This record as markdown: /tools/io-github-kivanccakmak-yaver/phone-project-export.md
What phone_project_export does on Yaver
AI agents call phone_project_export to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | |
containerize | boolean | — | Include Dockerfile/docker-compose/.env scaffold for own-cloud or Yaver Cloud deploy paths |
include_data | boolean | — | Include local.db so runtime rows survive import/push |
Parameters from the server's own tool schema.
Why phone_project_export is rated Low
This tool reads and packages existing project artifacts into a tgz archive for export. It does not create, modify, or delete data. However, severity is medium because it exports potentially sensitive configuration including auth details, schema, and seed data — misuse could expose credentials or proprietary database structure.
From the tool's definition 'Return a tgz of the portable manifest' and 'Base64-encoded so it round-trips through JSON' — the tool reads and exports project data (schema, auth, seed, config, DDL) without modifying anything.
Attacks that exploit this kind of access
The rule that runs phone_project_export 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_export, this is the rule to start with:
phone_project_export is read-only, so it stays allowed. 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_export call is checked against it from then on.
Questions about phone_project_export
Return a tgz of the project's portable manifest (schema + auth + seed + config + generated DDL). Base64-encoded so it round-trips through JSON. Supports include_data and containerize so MCP clients can export the exact same local-first backend bundle the mobile app and CLI use. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
phone_project_export accepts 3 parameters: slug, containerize, include_data. 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_export: 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_export is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the phone_project_export 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_export. 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_export 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