remove_landing_page_domain
Remove the dedicated custom domain from one landing page. The page keeps its workspace and Sequenzy fallback URLs.
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/remove-landing-page-domain.md
What remove_landing_page_domain does on Sequenzy Mcp
AI agents call remove_landing_page_domain to permanently remove resources in Sequenzy Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_landing_page_domain is rated Critical
Removes a custom domain configuration irreversibly from a landing page.
From the tool's definition Remove the dedicated custom domain from one landing page
Attacks that exploit this kind of access
The rule that runs remove_landing_page_domain safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sequenzy Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_landing_page_domain, this is the rule to start with:
remove_landing_page_domain is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Sequenzy Mcp, apply this rule, and every remove_landing_page_domain call is checked against it from then on.
Questions about remove_landing_page_domain
Remove the dedicated custom domain from one landing page. The page keeps its workspace and Sequenzy fallback URLs. It is categorised as a Destructive tool in the Sequenzy Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sequenzy MCP server in PolicyLayer and add a rule for remove_landing_page_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 Sequenzy Mcp. Nothing to install.
remove_landing_page_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_landing_page_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_landing_page_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_landing_page_domain is provided by the Sequenzy MCP server (Sequenzy/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sequenzy, and thousands of servers like it.
Across the catalogue