phone_project_import
Import a previously exported phone project tgz (base64-encoded). This restores a local SQLite-backed phone sandbox on this agent without promoting it anywhere else.
This record as markdown: /tools/io-github-kivanccakmak-yaver/phone-project-import.md
What phone_project_import does on Yaver
AI agents use phone_project_import 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 | — | Optional slug override on import |
skip_seed | boolean | — | Restore schema/auth but skip seed/live data application |
on_conflict | string | — | reject | rename | overwrite |
tarball_b64 | string | Yes | Base64-encoded .tgz produced by phone_project_export |
Parameters from the server's own tool schema.
Why phone_project_import is rated Medium
This is a Write operation because it creates or modifies data (SQLite database) reversibly. It is not Destructive because the action can theoretically be undone by deleting the imported sandbox or re-exporting. It is not Read because it performs a write/restore action, not mere retrieval. The 'local' scope and lack of external promotion limits blast radius to medium severity rather than high.
From the tool's definition The tool accepts a base64-encoded tgz archive to import/restore a 'phone project' into 'a local SQLite-backed phone sandbox.' This modifies local database state by creating or populating a SQLite database from the imported archive.
Attacks that exploit this kind of access
The rule that runs phone_project_import 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_import, this is the rule to start with:
phone_project_import 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_import call is checked against it from then on.
Questions about phone_project_import
Import a previously exported phone project tgz (base64-encoded). This restores a local SQLite-backed phone sandbox on this agent without promoting it anywhere else. 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_import accepts 4 parameters: slug, skip_seed, on_conflict, tarball_b64. Required: tarball_b64. 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_import: 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_import 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_import 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_import. 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_import 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