delete_post

Cancel and delete a post regardless of its current status (draft, scheduled, or posted).

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-post.md

WHAT IT DOES

What delete_post does on Postking Mcp

AI agents call delete_post 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_post is rated Critical

This tool permanently removes posts that may have been published, scheduled, or in draft form. Once deleted, the post cannot be recovered, making this a destructive action. While not as critical as financial transactions, the irreversible nature and potential business impact (removal of published content, loss of engagement) warrant a 'high' severity classification.

From the tool's definition Tool description explicitly states 'Cancel and delete a post regardless of its current status (draft, scheduled, or posted).' The verb 'delete' combined with 'regardless of status' indicates irreversible removal of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

delete_post Hidden

delete_post 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_post"
  ]
}

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_post call is checked against it from then on.

FAQ

Questions about delete_post

What does the delete_post tool do? +

Cancel and delete a post regardless of its current status (draft, scheduled, or posted). 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_post? +

Register the Postking MCP server in PolicyLayer and add a rule for delete_post: 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_post? +

delete_post 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_post? +

Yes. Add a rate_limit block to the delete_post 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_post completely? +

Set action: deny in the PolicyLayer policy for delete_post. 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_post? +

delete_post 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_post does on Postking Mcp

Why delete_post is rated Critical

The rule that runs delete_post safely

Questions about delete_post

More on Postking, and thousands of servers like it.