phone_project_create
Create a portable SQLite-first Yaver Serverless Mobile Workspace project. Writes yaver.serverless.yaml, schema.yaml, auth.yaml, seed.json, and local.db under ~/.yaver/phone-projects/<slug>/. The manifest can later migrate to the user's own hardware or Yaver Cloud without changing the app contract.
This record as markdown: /tools/io-github-kivanccakmak-yaver/phone-project-create.md
What phone_project_create does on Yaver
AI agents use phone_project_create 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 |
|---|---|---|---|
name | string | Yes | Human-readable project name |
slug | string | — | Optional directory slug (derived from name if omitted) |
template | string | — | One of: blank, crud, todos, notes |
Parameters from the server's own tool schema.
Why phone_project_create is rated Medium
Creates and writes multiple configuration and database files; reversible but establishes project state with wide blast radius.
From the tool's definition Create... Writes yaver.serverless.yaml, schema.yaml, auth.yaml, seed.json, local.db
Risk signalsAccepts raw HTML/template content (template)
Attacks that exploit this kind of access
The rule that runs phone_project_create 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_create, this is the rule to start with:
phone_project_create 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_create call is checked against it from then on.
Questions about phone_project_create
Create a portable SQLite-first Yaver Serverless Mobile Workspace project. Writes yaver.serverless.yaml, schema.yaml, auth.yaml, seed.json, and local.db under ~/.yaver/phone-projects/<slug>/. The manifest can later migrate to the user's own hardware or Yaver Cloud without changing the app contract. 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_create accepts 3 parameters: name, slug, template. Required: name. 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_create: 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_create 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_create 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_create. 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_create 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