yaver_report_complete
Record that the requested work is fully complete and verified. Call this ONLY after you have completed the user's requested work and run the relevant checks; it is the sole automatic route to Yaver's Review state. Do not call it for a normal conversational reply, a partial implementation, an open...
This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-report-complete.md
What yaver_report_complete does on Yaver
AI agents use yaver_report_complete 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 |
|---|---|---|---|
summary | string | — | Short verified completion summary for the review card; include the most meaningful evidence, not terminal output. |
Parameters from the server's own tool schema.
Why yaver_report_complete is rated Medium
Updates workflow state to 'Review'; reversible status change with moderate blast radius.
From the tool's definition Record that the requested work is fully complete and verified
Attacks that exploit this kind of access
The rule that runs yaver_report_complete 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 yaver_report_complete, this is the rule to start with:
yaver_report_complete 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 yaver_report_complete call is checked against it from then on.
Questions about yaver_report_complete
Record that the requested work is fully complete and verified. Call this ONLY after you have completed the user's requested work and run the relevant checks; it is the sole automatic route to Yaver's Review state. Do not call it for a normal conversational reply, a partial implementation, an open question, a failed check, or merely because your process is about to exit. If you do not call it, the turn lands in 'Your turn' and the human can continue in the same runner conversation. 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.
yaver_report_complete accepts 1 parameter: summary. 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 yaver_report_complete: 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.
yaver_report_complete 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 yaver_report_complete 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 yaver_report_complete. 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.
yaver_report_complete 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