delete_checkpoint

Delete a checkpoint from a milestone. Cannot delete completed checkpoints or checkpoints that others depend on.

Server Clink MCP Server voxos-ai-inc/clink-mcp-server-python
Category Destructive
Risk class Critical
Parameters 00 required

What delete_checkpoint does on Clink MCP Server

AI agents call delete_checkpoint to permanently remove resources in Clink MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_checkpoint needs a policy

Although the tool has safeguards (cannot delete completed checkpoints or those with dependencies), the core function is to irreversibly remove data from the project collaboration system. Deletion is irreversible and cannot be undone by normal means, placing this in the Destructive category.

From the tool's definition Tool name is 'delete_checkpoint' and description states it 'Delete[s] a checkpoint from a milestone.' The verb 'delete' combined with the irreversible nature of removing a checkpoint from project tracking data indicates a destructive operation.

Questions about delete_checkpoint

What does the delete_checkpoint tool do? +

Delete a checkpoint from a milestone. Cannot delete completed checkpoints or checkpoints that others depend on. It is categorised as a Destructive tool in the Clink MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_checkpoint? +

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

delete_checkpoint is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_checkpoint? +

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

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

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.