project_wizard_start
Start a new fullstack project wizard session. Returns sessionId + first question. Call project_wizard_answer repeatedly, then project_wizard_generate.
This record as markdown: /tools/io-github-kivanccakmak-yaver/project-wizard-start.md
What project_wizard_start does on Yaver
AI agents use project_wizard_start 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.
Why project_wizard_start is rated Medium
This tool creates a new wizard session (a stateful resource), which is a Write operation. It doesn't execute code or delete anything; it initializes a guided project creation flow. Misuse could lead to unwanted project scaffolding, but the blast radius is moderate since no code is deployed yet — that happens downstream via project_wizard_generate.
From the tool's definition 'Start a new fullstack project wizard session' and 'Returns sessionId + first question' — initiates a new session/resource creation
Attacks that exploit this kind of access
The rule that runs project_wizard_start 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_start, this is the rule to start with:
project_wizard_start 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_start call is checked against it from then on.
Questions about project_wizard_start
Start a new fullstack project wizard session. Returns sessionId + first question. Call project_wizard_answer repeatedly, then project_wizard_generate. 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.
Register the Yaver MCP server in PolicyLayer and add a rule for project_wizard_start: 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_start 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_start 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_start. 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_start 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