delete_lp_version
Permanently delete a historical landing page version. Cannot delete the published version or the only remaining version (the server will reject those). Pass confirm: true to proceed.
This record as markdown: /tools/io-github-bitsandtea-postking-mcp/delete-lp-version.md
What delete_lp_version does on Postking Mcp
AI agents call delete_lp_version 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_lp_version is rated Critical
This tool irreversibly deletes landing page versions and cannot be undone. Although it has safeguards (cannot delete published or sole remaining version), it still permanently removes data from the system. Destructive is more severe than Write and is the appropriate category for permanent deletion operations.
From the tool's definition The tool description explicitly states 'Permanently delete a historical landing page version' and requires 'confirm: true to proceed', indicating irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs delete_lp_version 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_lp_version, this is the rule to start with:
delete_lp_version 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_lp_version call is checked against it from then on.
Questions about delete_lp_version
Permanently delete a historical landing page version. Cannot delete the published version or the only remaining version (the server will reject those). Pass confirm: true to proceed. 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_lp_version: 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_lp_version 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_lp_version 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_lp_version. 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_lp_version 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