init_project
Scaffold a new project directly (without the interactive wizard). Picks services.yaml presets + writes .yaver/config.yaml + kicks off create-next-app in the background.
This record as markdown: /tools/io-github-kivanccakmak-yaver/init-project.md
What init_project does on Yaver
AI agents use init_project 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 |
|---|---|---|---|
opts | string | Yes | JSON: {name, parentDir, stack, db, auth, payments, template, orm, services} |
Parameters from the server's own tool schema.
Why init_project is rated Medium
The tool creates and writes configuration files (.yaver/config.yaml) and scaffolds a new project structure, which are reversible write operations. While it initiates a background process (create-next-app), the effects are primarily file creation and project initialization rather than irreversible destruction or external state changes with high blast radius.
From the tool's definition Tool description states it "writes .yaver/config.yaml" and "kicks off create-next-app in the background," indicating creation and modification of project files and initiation of a build process.
Attacks that exploit this kind of access
The rule that runs init_project 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 init_project, this is the rule to start with:
init_project 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 init_project call is checked against it from then on.
Questions about init_project
Scaffold a new project directly (without the interactive wizard). Picks services.yaml presets + writes .yaver/config.yaml + kicks off create-next-app in the background. 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.
init_project accepts 1 parameter: opts. Required: opts. 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 init_project: 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.
init_project 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 init_project 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 init_project. 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.
init_project 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