Release a custom domain mapping. Traffic to the domain will no longer route to Run402.
AI agents call remove_custom_domain 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.
Releasing a custom domain mapping breaks existing DNS/routing for live traffic. This cannot be undone without re-adding and re-propagating the domain, and in the interim period users/customers cannot reach the service. This qualifies as Destructive due to its irreversible and potentially service-disrupting nature.
From the tool's definition 'Release a custom domain mapping. Traffic to the domain will no longer route to Run402.' — this removes the domain routing configuration, which is an irreversible action that immediately disrupts live traffic.
Attacks that exploit this kind of access
Release a custom domain mapping. Traffic to the domain will no longer route to Run402. 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 remove_custom_domain: 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.
remove_custom_domain 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 remove_custom_domain 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 remove_custom_domain. 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.
remove_custom_domain 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 →