Unpublish a landing page, removing it from public access. The page returns to draft status. Requires a two-step confirmation: first call returns a confirmation_token, second call with the token performs the unpublish.
Part of the PO6 Mailbox server.
Free to start. No card required.
AI agents may call unpublish_landing_page to permanently remove or destroy resources in PO6 Mailbox. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call unpublish_landing_page in a loop, permanently destroying resources in PO6 Mailbox. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"unpublish_landing_page"
]
}See the full PO6 Mailbox policy for all 39 tools.
These attack patterns abuse exactly the kind of access unpublish_landing_page gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Unpublish a landing page, removing it from public access. The page returns to draft status. Requires a two-step confirmation: first call returns a confirmation_token, second call with the token performs the unpublish.. It is categorised as a Destructive tool in the PO6 Mailbox MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PO6 Mailbox MCP server in PolicyLayer and add a rule for unpublish_landing_page: 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 PO6 Mailbox. Nothing to install.
unpublish_landing_page 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 unpublish_landing_page 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 unpublish_landing_page. 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.
unpublish_landing_page is provided by the PO6 Mailbox MCP server (https://mcp.po6.com). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 39 PO6 Mailbox tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.