blog_cta_delete

Remove ONE CTA from a blog article by its ctaId, leaving every other CTA untouched. Removing the 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/blog-cta-delete.md

WHAT IT DOES

What blog_cta_delete does on Postking Mcp

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

Irreversibly deletes content from published blog articles without restoration capability.

From the tool's definition Remove ONE CTA from a blog article, Removing the article

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

blog_cta_delete Hidden

blog_cta_delete 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": [
    "blog_cta_delete"
  ]
}

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

FAQ

Questions about blog_cta_delete

What does the blog_cta_delete tool do? +

Remove ONE CTA from a blog article by its ctaId, leaving every other CTA untouched. Removing the 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 blog_cta_delete? +

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

blog_cta_delete 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 blog_cta_delete? +

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

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

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

Why blog_cta_delete is rated Critical

The rule that runs blog_cta_delete safely

Questions about blog_cta_delete

More on Postking, and thousands of servers like it.