phone_project_design_patch
Edit the app layout/design WITHOUT touching schema or data. Pass either patches (preferred) or a full design object. Node ids: nav, title, quickadd, list. patches[] shapes: {"op":"set","nodeId":"quickadd","props":{"marginTop":16,"hidden":false,"title":"...","reorderable":true,"swipeDelete":true}}...
This record as markdown: /tools/io-github-kivanccakmak-yaver/phone-project-design-patch.md
What phone_project_design_patch does on Yaver
AI agents use phone_project_design_patch 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 | |
design | object | — | Full PhoneDesign {layout,ui} — replaces the design layer |
patches | array | — | PhoneDesignPatch[] — preferred |
Parameters from the server's own tool schema.
Why phone_project_design_patch is rated Medium
The tool creates or modifies data reversibly: it changes UI layout properties, node visibility, and element ordering through patch operations. While it explicitly does NOT touch schema or data, it performs create/update-like operations on design state. This is a Write operation (reversible, non-destructive).
From the tool's definition Tool description explicitly states it 'Edit the app layout/design' by passing 'patches' with operations like 'set', 'move', and 'enable' that modify UI properties (marginTop, hidden, title, reorderable, swipeDelete) and element positioning.
Attacks that exploit this kind of access
The rule that runs phone_project_design_patch 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_design_patch, this is the rule to start with:
phone_project_design_patch 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_design_patch call is checked against it from then on.
Questions about phone_project_design_patch
Edit the app layout/design WITHOUT touching schema or data. Pass either patches (preferred) or a full design object. Node ids: nav, title, quickadd, list. patches[] shapes: {"op":"set","nodeId":"quickadd","props":{"marginTop":16,"hidden":false,"title":"...","reorderable":true,"swipeDelete":true}} | {"op":"move","nodeId":"quickadd","beforeId":"list"} (beforeId empty = end) | {"op":"enable","nodeId":"list","affordance":"reorder|swipe"}. This is the spec-patch seam — it never collides with the app's own drag. 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_design_patch accepts 3 parameters: slug, design, patches. 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_design_patch: 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_design_patch 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_design_patch 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_design_patch. 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_design_patch 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