add_checkpoint · Clink MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_checkpoint does on Clink MCP Server

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

WHY IT NEEDS A POLICY

Why add_checkpoint needs a policy

The name 'add_checkpoint' indicates a write operation that creates or modifies checkpoint data within a collaboration and project tracking system. This is reversible (checkpoints can be archived or modified), so it falls under Write rather than Destructive. However, confidence is reduced to 0.65 because the description is empty and the actual semantics depend on context.

From the tool's definition Tool name 'add_checkpoint' in a project tracking and milestone management system suggests creating or modifying checkpoint records. The sibling tool 'complete_checkpoint' indicates checkpoints are data entities that can be managed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_checkpoint Rate-limited

add_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": {
    "add_checkpoint": {
      "limits": [
        {
          "counter": "add_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 Clink MCP Server, so you can run agents against it safely.

FAQ

Questions about add_checkpoint

What does the add_checkpoint tool do? +

add_checkpoint. It is categorised as a Write tool in the Clink 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 add_checkpoint? +

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

What risk level is add_checkpoint? +

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

Can I rate-limit add_checkpoint? +

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

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

add_checkpoint is provided by the Clink MCP Server MCP server (voxos-ai-inc/clink-mcp-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.