delete_blog_article

Permanently delete a blog article.

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-blog-article.md

WHAT IT DOES

What delete_blog_article does on Postking Mcp

AI agents call delete_blog_article 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_blog_article is rated Critical

This tool irreversibly removes blog article data with no undo mechanism. While the blast radius is limited to blog content (not financial or system-critical), permanent deletion of published content can cause reputational harm, loss of SEO value, and inability to recover the data. This warrants 'high' severity and the Destructive category.

From the tool's definition Tool name is 'delete_blog_article' and description states 'Permanently delete a blog article.' The word 'Permanently' and 'delete' explicitly indicate irreversible data destruction.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

delete_blog_article Hidden

delete_blog_article 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_blog_article"
  ]
}

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

FAQ

Questions about delete_blog_article

What does the delete_blog_article tool do? +

Permanently delete a blog article. 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_blog_article? +

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

delete_blog_article 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_blog_article? +

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

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

delete_blog_article 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_blog_article does on Postking Mcp

Why delete_blog_article is rated Critical

The rule that runs delete_blog_article safely

Questions about delete_blog_article

More on Postking, and thousands of servers like it.