save_checkpoint · KeepGoing MCP Server MCP: Risk & Policy

WHAT IT DOES

What save_checkpoint does on KeepGoing MCP Server

AI agents use save_checkpoint to create or update resources in KeepGoing MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your KeepGoing MCP Server environment.

WHY IT NEEDS A POLICY

Why save_checkpoint needs a policy

save_checkpoint is a Write operation—it creates or modifies checkpoint data that represents project state and progress. This is reversible (checkpoints can be overwritten or deleted by other operations), has no destructive capability, does not execute arbitrary code or commands, and does not involve financial transactions.

From the tool's definition Tool description states 'Save a development checkpoint' and 'helps the next session (or developer) pick up exactly where you left off', indicating it creates/stores data (checkpoint records) in a persistent system without irreversible deletion or external…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_checkpoint Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_checkpoint": {
      "limits": [
        {
          "counter": "save_checkpoint_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches KeepGoing MCP Server, so you can run agents against it safely.

FAQ

Questions about save_checkpoint

What does the save_checkpoint tool do? +

Save a development checkpoint. Call this after completing a task or meaningful piece of work, not just at end of session. Each checkpoint helps the next session (or developer) pick up exactly where you left off. It is categorised as a Write tool in the KeepGoing MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_checkpoint? +

Register the KeepGoing MCP Server MCP server in PolicyLayer and add a rule for save_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 KeepGoing MCP Server. Nothing to install.

What risk level is save_checkpoint? +

save_checkpoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit save_checkpoint? +

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

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

save_checkpoint is provided by the KeepGoing MCP Server MCP server (keepgoing-dev/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.