Reset a Kinsta site to a fresh WordPress install. This removes all existing data.
AI agents call kinsta.sites.reset 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.
This tool irreversibly deletes all site data and configuration by resetting to a fresh install. There is no undo mechanism—all user content, database, files, and customizations are permanently lost. This represents maximum blast radius for data destruction on a live hosting platform. While not financial, destructive actions take precedence over execute-category risks due to their irreversible nature.
From the tool's definition Tool description explicitly states: 'Reset a Kinsta site to a fresh WordPress install. This removes all existing data.' The word 'removes' combined with 'all existing data' and the irreversible nature of a reset operation confirms this is a destructive action.
Attacks that exploit this kind of access
Reset a Kinsta site to a fresh WordPress install. This removes all existing data. 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.sites.reset: 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.sites.reset 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.sites.reset 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.sites.reset. 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.sites.reset 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 →