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...
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.
An AI agent can call phone_project_schema faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
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.