Release a custom subdomain. The URL will stop serving content.
AI agents call delete_subdomain to permanently remove resources in Run402 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This action permanently removes a subdomain configuration, causing the associated URL to cease functioning. This is irreversible — once deleted, the subdomain must be re-added from scratch. The blast radius includes service disruption for users/applications dependent on that subdomain, making it a Destructive action rather than merely a Write operation.
From the tool's definition Tool name 'delete_subdomain' combined with description 'Release a custom subdomain. The URL will stop serving content' indicates irreversible deletion of a domain binding that cannot be undone.
Attacks that exploit this kind of access
Release a custom subdomain. The URL will stop serving content. It is categorised as a Destructive tool in the Run402 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Run402 MCP server in PolicyLayer and add a rule for delete_subdomain: 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 Run402. Nothing to install.
delete_subdomain 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 delete_subdomain 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 delete_subdomain. 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.
delete_subdomain is provided by the Run402 MCP server (kychee-com/run402). 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 →