Update the machine-aware yaver code control-plane state on the local or a remote owned Yaver machine. Supports runner/model/orchestration/work-mode/attached machine/repo fields and an optional BYOK block for OpenCode-backed coding (OpenRouter, custom OpenAI-compatible providers, remote Ollama). R...
AI agents use code_config_set 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 |
|---|---|---|---|
model | string | — | Model id for the selected runner |
runner | string | — | Runner override such as claude, codex, or opencode |
base_url | string | — | Provider base URL such as https://openrouter.ai/api/v1 |
provider | string | — | Preferred provider id for opencode-backed BYOK flows, e.g. openrouter |
device_id | string | — | Optional remote device ID |
repo_path | string | — | Set the effective repo/workdir for the current local or attached target |
work_mode | string | — | |
plan_model | string | — | |
build_model | string | — | |
repo_remote | boolean | — | |
small_model | string | — | |
byok_api_key | string | — |
Parameters from the server's own tool schema.
An AI agent can call code_config_set 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 URL/endpoint input (base_url) · High parameter count (16 properties)
Attacks that exploit this kind of access
Update the machine-aware yaver code control-plane state on the local or a remote owned Yaver machine. Supports runner/model/orchestration/work-mode/attached machine/repo fields and an optional BYOK block for OpenCode-backed coding (OpenRouter, custom OpenAI-compatible providers, remote Ollama). Returns the updated code summary. 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.
code_config_set accepts 12 parameters: model, runner, base_url, provider, device_id, repo_path, work_mode, plan_model, build_model, repo_remote, small_model, byok_api_key. 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 code_config_set: 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.
code_config_set 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 code_config_set 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 code_config_set. 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.
code_config_set 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.