Merge runtime/provider updates into .yaver/project.yaml, optionally connect provider accounts, run manifest apply, and plan or run mobile sandbox promotions. Supports either a project directory or a phoneSlug for phone-first sandboxes.
AI agents use project_runtime_apply 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 |
|---|---|---|---|
env | object | — | |
auth | string | — | |
jobs | array | — | |
name | string | — | |
stack | string | — | |
dryRun | boolean | — | |
backend | string | — | |
domains | array | — | |
runtime | object | — | |
directory | string | — | |
phoneSlug | string | — | |
placement | object | — |
Parameters from the server's own tool schema.
An AI agent can call project_runtime_apply faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.
Risk signalsAccepts file system path (directory) · Handles credentials or secrets (auth) · High parameter count (15 properties)
Attacks that exploit this kind of access
Merge runtime/provider updates into .yaver/project.yaml, optionally connect provider accounts, run manifest apply, and plan or run mobile sandbox promotions. Supports either a project directory or a phoneSlug for phone-first sandboxes. 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.
project_runtime_apply accepts 12 parameters: env, auth, jobs, name, stack, dryRun, backend, domains, runtime, directory, phoneSlug, placement. 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 project_runtime_apply: 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.
project_runtime_apply 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 project_runtime_apply 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 project_runtime_apply. 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.
project_runtime_apply 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.