phone_project_widget_list
List the addressable UI widget nodes of a phone project's app (the mini-figma layer) with their current overrides. Node ids: nav, title, quickadd, list. Use this before phone_project_design_patch to see what you can change.
This record as markdown: /tools/io-github-kivanccakmak-yaver/phone-project-widget-list.md
What phone_project_widget_list does on Yaver
AI agents call phone_project_widget_list to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes |
Parameters from the server's own tool schema.
Why phone_project_widget_list is rated Low
This tool retrieves and displays data about a phone project's UI widget hierarchy and their current state. It has no side effects, creates no data, executes no code, deletes nothing, and moves no money. It is purely informational, used to inspect the current state before making changes with other tools.
From the tool's definition Tool description explicitly states 'List the addressable UI widget nodes' and 'Use this before phone_project_design_patch to see what you can change.' The verb 'list' and the instructional context ('before...to see') indicate this is a query operation that…
Attacks that exploit this kind of access
The rule that runs phone_project_widget_list 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_widget_list, this is the rule to start with:
phone_project_widget_list is read-only, so it stays allowed. 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_widget_list call is checked against it from then on.
Questions about phone_project_widget_list
List the addressable UI widget nodes of a phone project's app (the mini-figma layer) with their current overrides. Node ids: nav, title, quickadd, list. Use this before phone_project_design_patch to see what you can change. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
phone_project_widget_list accepts 1 parameter: slug. 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_widget_list: 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_widget_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the phone_project_widget_list 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_widget_list. 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_widget_list 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