agloop_create_checkpoint · Agloop MCP: Risk & Policy

WHAT IT DOES

What agloop_create_checkpoint does on Agloop

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

WHY IT NEEDS A POLICY

Why agloop_create_checkpoint needs a policy

Creating a checkpoint is a reversible write operation that captures and stores the current system state. It does not delete data (not Destructive), execute arbitrary code (not Execute), move money (not Financial), or merely read existing data (not Read).

From the tool's definition Tool name 'agloop_create_checkpoint' and description 'Create a checkpoint of the current state for recovery' indicate this creates and persists a new data record (checkpoint). The 'COORDINATOR ONLY' restriction suggests administrative write access.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

agloop_create_checkpoint Rate-limited

agloop_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": {
    "agloop_create_checkpoint": {
      "limits": [
        {
          "counter": "agloop_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 Agloop, so you can run agents against it safely.

FAQ

Questions about agloop_create_checkpoint

What does the agloop_create_checkpoint tool do? +

Create a checkpoint of the current state for recovery. COORDINATOR ONLY. It is categorised as a Write tool in the Agloop MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on agloop_create_checkpoint? +

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

What risk level is agloop_create_checkpoint? +

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

Can I rate-limit agloop_create_checkpoint? +

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

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

agloop_create_checkpoint is provided by the Agloop MCP server (zebbern/agloop-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.