create_checkpoint · Vigentic MCP: Risk & Policy

WHAT IT DOES

What create_checkpoint does on Vigentic MCP

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

WHY IT NEEDS A POLICY

Why create_checkpoint needs a policy

This tool creates a new checkpoint (a saved state record), which is a reversible write operation. It doesn't execute code or delete data, but it does create and persist new data structures representing file states. The 'without saving buffers implicitly' clarification confirms it creates a checkpoint artifact rather than modifying the actual files themselves.

From the tool's definition Tool name 'create_checkpoint' and description 'Create a saved-state checkpoint for explicit files without saving buffers implicitly' indicate the tool creates a checkpoint record representing the current state of specified files.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_checkpoint Rate-limited

create_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": {
    "create_checkpoint": {
      "limits": [
        {
          "counter": "create_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 Vigentic MCP, so you can run agents against it safely.

FAQ

Questions about create_checkpoint

What does the create_checkpoint tool do? +

Create a saved-state checkpoint for explicit files without saving buffers implicitly. It is categorised as a Write tool in the Vigentic MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_checkpoint? +

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

What risk level is create_checkpoint? +

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

Can I rate-limit create_checkpoint? +

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

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

create_checkpoint is provided by the Vigentic MCP server (munozu/vigentic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.