morning_rollback

Revert a single task's commits (git revert, new commit chain — never destructive). The task must have recorded CommitSHAs. Returns the new HEAD sha. Use only when the user explicitly asks to undo a task.

Server Yaver yaver-cli
Category Read
Risk class Low
Parameters 22 required

What morning_rollback does on Yaver

AI agents call morning_rollback to retrieve information from Yaver without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
run_id string Yes
task_id string Yes

Parameters from the server's own tool schema.

Why morning_rollback needs a policy

Even though morning_rollback 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.

Questions about morning_rollback

What does the morning_rollback tool do? +

Revert a single task's commits (git revert, new commit chain — never destructive). The task must have recorded CommitSHAs. Returns the new HEAD sha. Use only when the user explicitly asks to undo a task. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does morning_rollback accept? +

morning_rollback accepts 2 parameters: run_id, task_id. Required: run_id, task_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on morning_rollback? +

Register the Yaver MCP server in PolicyLayer and add a rule for morning_rollback: 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.

What risk level is morning_rollback? +

morning_rollback is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit morning_rollback? +

Yes. Add a rate_limit block to the morning_rollback 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.

How do I block morning_rollback completely? +

Set action: deny in the PolicyLayer policy for morning_rollback. 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.

What MCP server provides morning_rollback? +

morning_rollback 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.