kinsta.backups.delete

Delete a backup. This action cannot be undone.

Server Kinsta MCP Server jacob-hartmann/kinsta-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What kinsta.backups.delete does on Kinsta MCP Server

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

Why kinsta.backups.delete needs a policy

This tool irreversibly deletes backup data, which cannot be recovered once removed. Backups are critical infrastructure components for disaster recovery and data protection. An AI agent misusing this tool could cause permanent loss of site data recovery options, creating significant operational impact. The explicit 'cannot be undone' warning confirms this meets the Destructive category definition.

From the tool's definition Tool description explicitly states 'Delete a backup. This action cannot be undone.' The name 'kinsta.backups.delete' combined with the irreversible nature documented in the description clearly indicates a destructive operation.

Questions about kinsta.backups.delete

What does the kinsta.backups.delete tool do? +

Delete a backup. This action cannot be undone. It is categorised as a Destructive tool in the Kinsta 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 kinsta.backups.delete? +

Register the Kinsta MCP Server MCP server in PolicyLayer and add a rule for kinsta.backups.delete: 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 Kinsta MCP Server. Nothing to install.

What risk level is kinsta.backups.delete? +

kinsta.backups.delete 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 kinsta.backups.delete? +

Yes. Add a rate_limit block to the kinsta.backups.delete 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 kinsta.backups.delete completely? +

Set action: deny in the PolicyLayer policy for kinsta.backups.delete. 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 kinsta.backups.delete? +

kinsta.backups.delete is provided by the Kinsta MCP Server MCP server (jacob-hartmann/kinsta-mcp). 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.