Restore an environment from a backup. This will overwrite the current environment. Returns an operation_id.
AI agents call kinsta.backups.restore 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.
Restoring from a backup overwrites the current environment entirely, destroying all current data and state irreversibly. This is a destructive, unrecoverable operation — any changes made since the backup point are permanently lost. The blast radius is critical as it affects an entire WordPress hosting environment.
From the tool's definition 'Restore an environment from a backup. This will overwrite the current environment.'
Attacks that exploit this kind of access
Restore an environment from a backup. This will overwrite the current environment. Returns an operation_id. 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.
Register the Kinsta MCP Server MCP server in PolicyLayer and add a rule for kinsta.backups.restore: 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.
kinsta.backups.restore 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 kinsta.backups.restore 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 kinsta.backups.restore. 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.
kinsta.backups.restore 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.
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 →