New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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}}...

SERVERYaver SOURCEyaver-cli
Medium RISK CLASS
Category Write
Parameters 31 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about phone_project_design_patch

What does the phone_project_design_patch tool do? +

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.

What parameters does phone_project_design_patch accept? +

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.

How do I enforce a policy on phone_project_design_patch? +

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.

What risk level is phone_project_design_patch? +

phone_project_design_patch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit phone_project_design_patch? +

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.

How do I block phone_project_design_patch completely? +

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.

What MCP server provides phone_project_design_patch? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.