Remove a custom hostname from a site. Cannot be undone.
AI agents call sitebay_remove_custom_hostname to permanently remove resources in SiteBay MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a custom hostname is a destructive action that permanently alters site DNS routing and cannot be reversed without manual reconfiguration. This meets the Destructive category definition as an action that 'cannot be undone.' The severity is high because misconfiguration could take a site offline or redirect traffic incorrectly, impacting availability and user access.
From the tool's definition Tool description explicitly states "Cannot be undone", indicating irreversible deletion/modification of site configuration.
Attacks that exploit this kind of access
Remove a custom hostname from a site. Cannot be undone. It is categorised as a Destructive tool in the SiteBay MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SiteBay MCP Server MCP server in PolicyLayer and add a rule for sitebay_remove_custom_hostname: 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 SiteBay MCP Server. Nothing to install.
sitebay_remove_custom_hostname 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 sitebay_remove_custom_hostname 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 sitebay_remove_custom_hostname. 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.
sitebay_remove_custom_hostname is provided by the SiteBay MCP Server MCP server (sitebay/sitebay-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 →