workspace_init
Wire every app declared in yaver.workspace.yaml: scaffold init.md, env-check, per-app setup. Call workspace_scaffold first if no manifest exists. Idempotent — re-runs skip already-initialised apps unless force=true.
This record as markdown: /tools/io-github-kivanccakmak-yaver/workspace-init.md
What workspace_init does on Yaver
AI agents invoke workspace_init to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
root | string | — | Repo root. Defaults to agent CWD. |
force | boolean | — | Overwrite existing init.md files. |
dryRun | boolean | — | |
onlyApp | string | — | Restrict to a single app name. |
autoinitPrompt | boolean | — | Include per-app `yaver autoinit` hints in the result. |
Parameters from the server's own tool schema.
Why workspace_init is rated High
This tool executes initialization routines across multiple apps — scaffolding files, running environment checks, and performing per-app setup. These are active operations that trigger external processes and file system changes. While partly idempotent, it can still cause significant side effects (file creation, environment changes, app configuration) across an entire workspace.
From the tool's definition 'Wire every app declared in yaver.workspace.yaml: scaffold init.md, env-check, per-app setup' and 're-runs skip already-initialised apps unless force=true'
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs workspace_init 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 workspace_init, this is the rule to start with:
workspace_init stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 workspace_init call is checked against it from then on.
Questions about workspace_init
Wire every app declared in yaver.workspace.yaml: scaffold init.md, env-check, per-app setup. Call workspace_scaffold first if no manifest exists. Idempotent — re-runs skip already-initialised apps unless force=true. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
workspace_init accepts 5 parameters: root, force, dryRun, onlyApp, autoinitPrompt. 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 workspace_init: 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.
workspace_init is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the workspace_init 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 workspace_init. 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.
workspace_init 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.
Across the catalogue