Delete a single checkpoint without touching its plan. Args: - checkpointId (string)
AI agents call delete_checkpoint to permanently remove resources in Melo — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes checkpoint data from the Roblox Studio environment. Checkpoints are likely savepoints or versioned states of development work. Deletion cannot be undone and has no rollback mechanism mentioned. While the blast radius is scoped to a single checkpoint rather than project-wide data, the irreversible nature and loss of development history justifies the Destructive category and high severity.
From the tool's definition Tool name is 'delete_checkpoint' which explicitly performs deletion. Description states 'Delete a single checkpoint' — a destructive operation that removes data irreversibly.
Attacks that exploit this kind of access
Delete a single checkpoint without touching its plan. Args: - checkpointId (string). It is categorised as a Destructive tool in the Melo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Melo 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 Melo. Nothing to install.
delete_checkpoint is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
delete_checkpoint is provided by the Melo MCP server (yannyhl/linkedsword-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →