delete_landing_page
Permanently delete a landing page. Pass confirm: true to proceed — this is irreversible.
This record as markdown: /tools/io-github-bitsandtea-postking-mcp/delete-landing-page.md
What delete_landing_page does on Postking Mcp
AI agents call delete_landing_page 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_landing_page is rated Critical
This tool irreversibly deletes data (a landing page) and cannot be undone. It meets the definition of Destructive: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While it does not affect financial systems or execute arbitrary code, the permanent data loss and explicit irreversibility make it the most severe applicable category.
From the tool's definition Tool description explicitly states 'Permanently delete a landing page' and 'this is irreversible'. The name 'delete_landing_page' combined with the requirement to pass 'confirm: true' to proceed indicates an irreversible destructive action.
Attacks that exploit this kind of access
The rule that runs delete_landing_page 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_landing_page, this is the rule to start with:
delete_landing_page 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_landing_page call is checked against it from then on.
Questions about delete_landing_page
Permanently delete a landing page. Pass confirm: true to proceed — this is irreversible. 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_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 Postking Mcp. Nothing to install.
delete_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 delete_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 delete_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.
delete_landing_page 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