managed_git_checkpoint

Commit all current project changes to Yaver Managed Git and push to the managed main branch. Good before/after AI changes, deploys, or quality runs.

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

What managed_git_checkpoint does on Yaver

AI agents call managed_git_checkpoint 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
slug string
message string
work_dir string

Parameters from the server's own tool schema.

Why managed_git_checkpoint needs a policy

Even though managed_git_checkpoint 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 managed_git_checkpoint

What does the managed_git_checkpoint tool do? +

Commit all current project changes to Yaver Managed Git and push to the managed main branch. Good before/after AI changes, deploys, or quality runs. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does managed_git_checkpoint accept? +

managed_git_checkpoint accepts 3 parameters: slug, message, work_dir. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on managed_git_checkpoint? +

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

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

Can I rate-limit managed_git_checkpoint? +

Yes. Add a rate_limit block to the managed_git_checkpoint 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 managed_git_checkpoint completely? +

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

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