delete_domain
Remove a custom domain. Connected blogs and landing pages are unlinked but not deleted.
This record as markdown: /tools/io-github-bitsandtea-postking-mcp/delete-domain.md
What delete_domain does on Postking Mcp
AI agents call delete_domain to permanently remove resources in Postking Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_domain is rated Critical
This tool performs an irreversible deletion operation on a domain resource. Although the associated blogs and landing pages are preserved (only unlinked), the domain configuration itself is destroyed and cannot be undone without re-adding it as a new domain. This qualifies as Destructive rather than Write since deletion is not reversible.
From the tool's definition Tool name 'delete_domain' explicitly contains 'delete'; description states 'Remove a custom domain' indicating irreversible deletion. While connected content is not deleted, the domain itself is permanently removed and cannot be recovered.
Attacks that exploit this kind of access
The rule that runs delete_domain safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postking Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_domain, this is the rule to start with:
delete_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 Postking Mcp, apply this rule, and every delete_domain call is checked against it from then on.
Questions about delete_domain
Remove a custom domain. Connected blogs and landing pages are unlinked but not deleted. It is categorised as a Destructive tool in the Postking Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Postking MCP server in PolicyLayer and add a rule for delete_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 Postking Mcp. Nothing to install.
delete_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 delete_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 delete_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.
delete_domain is provided by the Postking MCP server (postking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Postking, and thousands of servers like it.
Across the catalogue