delete_side_page_version

SERVERPostking Mcp SOURCEpostking-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-bitsandtea-postking-mcp/delete-side-page-version.md

WHAT IT DOES

What delete_side_page_version does on Postking Mcp

AI agents call delete_side_page_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.

RISK

Why delete_side_page_version is rated Critical

Irreversibly removes page versions; deletion cannot be undone, affecting content history and recovery options.

From the tool's definition Permanently delete a historical side-page version. Cannot delete the only remaining version.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_side_page_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_side_page_version, this is the rule to start with:

delete_side_page_version Hidden

delete_side_page_version is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_side_page_version"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Postking Mcp, apply this rule, and every delete_side_page_version call is checked against it from then on.

FAQ

Questions about delete_side_page_version

What does the delete_side_page_version tool do? +

Permanently delete a historical side-page version. Deleting the current (draft) version is allowed and repoints the draft to the newest remaining version. Cannot delete the published (live) version or the only remaining version — the server will reject those and the rejection reason is returned as-is. 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.

How do I enforce a policy on delete_side_page_version? +

Register the Postking MCP server in PolicyLayer and add a rule for delete_side_page_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.

What risk level is delete_side_page_version? +

delete_side_page_version is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_side_page_version? +

Yes. Add a rate_limit block to the delete_side_page_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.

How do I block delete_side_page_version completely? +

Set action: deny in the PolicyLayer policy for delete_side_page_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.

What MCP server provides delete_side_page_version? +

delete_side_page_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.

KEEP EXPLORING

What delete_side_page_version does on Postking Mcp

Why delete_side_page_version is rated Critical

The rule that runs delete_side_page_version safely

Questions about delete_side_page_version

More on Postking, and thousands of servers like it.