phone_project_schema
Apply a declarative schema update to a phone project. Additive only — adds new tables / columns / indexes. Use the PhoneSchema shape: {tables:[{name,columns:[{name,type,primary,required,unique,default}], indexes:[{columns,unique}]}]}. Column types: text|int|bool|real|timestamp|json|uuid. Defaults...
This record as markdown: /tools/io-github-kivanccakmak-yaver/phone-project-schema.md
What phone_project_schema does on Yaver
AI agents use phone_project_schema 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 | |
schema | object | Yes |
Parameters from the server's own tool schema.
Why phone_project_schema is rated Medium
This tool creates or modifies data structure reversibly by adding tables, columns, and indexes to a project schema. It falls under Write category because it changes application state durably but without deletion/destruction.
From the tool's definition Applies a declarative schema update to a phone project with capability to add new tables, columns, and indexes using the PhoneSchema shape. The tool modifies data structure reversibly (additive only, no destructive operations mentioned).
Attacks that exploit this kind of access
The rule that runs phone_project_schema 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_schema, this is the rule to start with:
phone_project_schema 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_schema call is checked against it from then on.
Questions about phone_project_schema
Apply a declarative schema update to a phone project. Additive only — adds new tables / columns / indexes. Use the PhoneSchema shape: {tables:[{name,columns:[{name,type,primary,required,unique,default}], indexes:[{columns,unique}]}]}. Column types: text|int|bool|real|timestamp|json|uuid. Defaults: uuid|now|<literal>. 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_schema accepts 2 parameters: slug, schema. Required: slug, schema. 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_schema: 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_schema 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_schema 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_schema. 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_schema 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