project_wizard_answer
Submit an answer to the current wizard question. Returns the next question (or 'done' kind when complete).
This record as markdown: /tools/io-github-kivanccakmak-yaver/project-wizard-answer.md
What project_wizard_answer does on Yaver
AI agents call project_wizard_answer to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
answer | string | Yes | |
sessionId | string | Yes | |
questionId | string | Yes |
Parameters from the server's own tool schema.
Why project_wizard_answer is rated Low
Even though project_wizard_answer only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs project_wizard_answer 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_answer, this is the rule to start with:
project_wizard_answer is read-only, so it stays allowed. 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_answer call is checked against it from then on.
Questions about project_wizard_answer
Submit an answer to the current wizard question. Returns the next question (or 'done' kind when complete). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
project_wizard_answer accepts 3 parameters: answer, sessionId, questionId. Required: answer, sessionId, questionId. 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_answer: 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_answer is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the project_wizard_answer 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_answer. 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_answer 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