Delete checkpoint metadata. The underlying backup is not affected. MCP Enabled.
AI agents call sitebay_delete_checkpoint to permanently remove resources in SiteBay MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs irreversible deletion of checkpoint metadata associated with WordPress site backups. While the description clarifies that the underlying backup itself is not affected, the deletion of checkpoint metadata is a destructive action that cannot be recovered.
From the tool's definition Tool name contains 'delete' and description states 'Delete checkpoint metadata'. Deletion is an irreversible operation that cannot be undone.
Attacks that exploit this kind of access
Delete checkpoint metadata. The underlying backup is not affected. MCP Enabled. It is categorised as a Destructive tool in the SiteBay MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SiteBay MCP Server MCP server in PolicyLayer and add a rule for sitebay_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 SiteBay MCP Server. Nothing to install.
sitebay_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 sitebay_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 sitebay_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.
sitebay_delete_checkpoint is provided by the SiteBay MCP Server MCP server (sitebay/sitebay-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 →