phone_project_web_approve
Approve a six-character connection code shown by a newly opened Home Screen shortcut. The shortcut receives a one-time, project-scoped token; it never receives the owner's Yaver token.
This record as markdown: /tools/io-github-kivanccakmak-yaver/phone-project-web-approve.md
What phone_project_web_approve does on Yaver
AI agents use phone_project_web_approve 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 |
|---|---|---|---|
code | string | Yes | |
slug | string | Yes |
Parameters from the server's own tool schema.
Why phone_project_web_approve is rated Medium
Grants access approval for a mobile shortcut connection, a reversible write action.
From the tool's definition Approve a six-character connection code, project-scoped token
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs phone_project_web_approve 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_web_approve, this is the rule to start with:
phone_project_web_approve 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_web_approve call is checked against it from then on.
Questions about phone_project_web_approve
Approve a six-character connection code shown by a newly opened Home Screen shortcut. The shortcut receives a one-time, project-scoped token; it never receives the owner's Yaver token. 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_web_approve accepts 2 parameters: code, slug. Required: code, 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_web_approve: 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_web_approve 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_web_approve 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_web_approve. 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_web_approve 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