project_wizard_generate
Materialise the scaffold for a completed wizard session. Returns the target directory + next-step checklist. Project folder is created at parentDir/<slug>.
This record as markdown: /tools/io-github-kivanccakmak-yaver/project-wizard-generate.md
What project_wizard_generate does on Yaver
AI agents use project_wizard_generate 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 |
|---|---|---|---|
parentDir | string | — | Parent directory for the new project (default: agent cwd) |
sessionId | string | Yes |
Parameters from the server's own tool schema.
Why project_wizard_generate is rated Medium
This tool creates new files and directories on the developer's system as a side effect of generating a project scaffold. This is reversible (folders and generated code can be deleted) and does not irreversibly destroy data, making it Write rather than Destructive.
From the tool's definition Tool creates project scaffold and folders at specified directory path (parentDir/<slug>). Description states 'Project folder is created' and 'Materialise the scaffold', indicating file system creation/modification.
Attacks that exploit this kind of access
The rule that runs project_wizard_generate 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 project_wizard_generate, this is the rule to start with:
project_wizard_generate 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 project_wizard_generate call is checked against it from then on.
Questions about project_wizard_generate
Materialise the scaffold for a completed wizard session. Returns the target directory + next-step checklist. Project folder is created at parentDir/<slug>. 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_wizard_generate accepts 2 parameters: parentDir, sessionId. Required: sessionId. 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_wizard_generate: 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_wizard_generate 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_wizard_generate 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_wizard_generate. 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_wizard_generate 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