Mark the current moment as a semantic checkpoint in the live-sync log. Use this when you've finished a coherent piece of work (feature complete, tests passing, a good place to stop) so reviewers can use the label as a compaction boundary. Optionally attach a structured trust assertion (e.g. tests...
Part of the Kai MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke kai_checkpoint_now to trigger processes or run actions in Kai. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
kai_checkpoint_now can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
kai_checkpoint_now:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Kai policy for all 18 tools.
Agents calling execute-class tools like kai_checkpoint_now have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
kai_checkpoint_now is one of the high-risk operations in Kai. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Mark the current moment as a semantic checkpoint in the live-sync log. Use this when you've finished a coherent piece of work (feature complete, tests passing, a good place to stop) so reviewers can use the label as a compaction boundary. Optionally attach a structured trust assertion (e.g. tests-pass) for the review trust badge. Does NOT run kai capture.. It is categorised as a Execute tool in the Kai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for kai_checkpoint_now. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Kai MCP server.
kai_checkpoint_now is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the kai_checkpoint_now rule in your Intercept 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 Intercept policy for kai_checkpoint_now. 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.
kai_checkpoint_now is provided by the Kai MCP server (kai-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept