Remove custom domains from an environment.
AI agents call kinsta.domains.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.
Deleting custom domains from a hosting environment is an irreversible action that cannot be undone without manual intervention or restoration from backups. This constitutes a destructive operation with significant blast radius—removing domains would break site accessibility and is not easily recoverable through the API.
From the tool's definition Tool name includes 'delete' and description states 'Remove custom domains from an environment.' The verb 'Remove' combined with 'delete' in the tool name indicates irreversible deletion of domain configuration.
Attacks that exploit this kind of access
Remove custom domains from an environment. 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.domains.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.
kinsta.domains.delete 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.domains.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.
Set action: deny in the PolicyLayer policy for kinsta.domains.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.
kinsta.domains.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.
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 →