complete_checkpoint · Clink MCP Server MCP: Risk & Policy

WHAT IT DOES

What complete_checkpoint does on Clink MCP Server

AI agents use complete_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 complete_checkpoint needs a policy

The tool modifies project tracking state by marking a checkpoint as complete, which is a reversible write operation. While the description is empty (lowering confidence), the name and context of milestone/checkpoint management tools within a collaboration platform indicate this performs a data modification. It's not destructive (checkpoint can likely be reopened), not financial, and not arbitrary code execution.

From the tool's definition Tool name 'complete_checkpoint' indicates a state-changing operation that modifies the status of a checkpoint from incomplete to complete. This is a write operation that updates existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

complete_checkpoint Rate-limited

complete_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": {
    "complete_checkpoint": {
      "limits": [
        {
          "counter": "complete_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 complete_checkpoint

What does the complete_checkpoint tool do? +

complete_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 complete_checkpoint? +

Register the Clink MCP Server MCP server in PolicyLayer and add a rule for complete_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 complete_checkpoint? +

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

Can I rate-limit complete_checkpoint? +

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

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

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