mobile_workspace_onboarding_select
Persist the selected Mobile Workspace development device and task runner as one Convex-backed primary choice. Validates that the runner is installed, authenticated, and operational on that owned device before writing. The workspace backend remains portable SQLite-first Yaver Serverless.
This record as markdown: /tools/io-github-kivanccakmak-yaver/mobile-workspace-onboarding-select.md
What mobile_workspace_onboarding_select does on Yaver
AI agents use mobile_workspace_onboarding_select 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 |
|---|---|---|---|
mode | string | — | Optional OpenCode mode. |
model | string | — | Optional model, for example deepseek/deepseek-v4-flash. |
device | string | Yes | Owned device ID, unique prefix, name, or alias. |
runner | string | Yes | |
provider | string | — | Optional OpenCode provider, for example deepseek. |
Parameters from the server's own tool schema.
Why mobile_workspace_onboarding_select is rated Medium
Creates or modifies configuration state by persisting device selection; reversible and non-destructive operation.
From the tool's definition Persist selected Mobile Workspace device and task runner as primary choice; validates before writing.
Attacks that exploit this kind of access
The rule that runs mobile_workspace_onboarding_select 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 mobile_workspace_onboarding_select, this is the rule to start with:
mobile_workspace_onboarding_select 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 mobile_workspace_onboarding_select call is checked against it from then on.
Questions about mobile_workspace_onboarding_select
Persist the selected Mobile Workspace development device and task runner as one Convex-backed primary choice. Validates that the runner is installed, authenticated, and operational on that owned device before writing. The workspace backend remains portable SQLite-first Yaver Serverless. 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.
mobile_workspace_onboarding_select accepts 5 parameters: mode, model, device, runner, provider. Required: device, runner. 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 mobile_workspace_onboarding_select: 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.
mobile_workspace_onboarding_select 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 mobile_workspace_onboarding_select 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 mobile_workspace_onboarding_select. 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.
mobile_workspace_onboarding_select 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