ghost_delete_post

THE RISK

Critical Risk

Why ghost_delete_post needs a policy

This tool irreversibly removes data (a blog post) from the CMS with no undo capability. While not financial in impact, the permanent deletion of published content represents a high-severity operation due to potential loss of business-critical blog posts, SEO impact, and inability to recover deleted content.

From the tool's definition Tool description explicitly states: 'Deletes a post from Ghost CMS by ID. This operation is permanent and cannot be undone.' The use of 'Deletes', 'permanent', and 'cannot be undone' are unambiguous indicators of destructive action.

Documented attack patterns abuse exactly the kind of access ghost_delete_post gives an agent:

POLICY

How to control ghost_delete_post

PolicyLayer is an MCP gateway — it sits between your AI agents and Ghost MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ghost_delete_post:

policy.json

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

ghost_delete_post disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Ghost MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Ghost MCP Server tools

Destructive ghost_delete_member Deletes a member from Ghost CMS by ID. This operation is permanent and cannot be undone. Destructive ghost_delete_newsletter Deletes a newsletter from Ghost CMS by ID. This operation is permanent and cannot be undon Destructive ghost_delete_page Deletes a page from Ghost CMS by ID. This operation is permanent and cannot be undone. Destructive ghost_delete_tag Deletes a tag from Ghost CMS by ID. This operation is permanent and cannot be undone. Destructive ghost_delete_tier Deletes a tier (membership level) from Ghost CMS by ID. This operation is permanent and ca Execute ghost_batch_operations Execute multiple Ghost operations in a single request Execute ghost_cache_management Manage resource cache Write ghost_create_member Creates a new member (subscriber) in Ghost CMS.

All 39 Ghost MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Ghost MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about ghost_delete_post

What does the ghost_delete_post tool do? +

Deletes a post from Ghost CMS by ID. This operation is permanent and cannot be undone. It is categorised as a Destructive tool in the Ghost MCP Server 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 ghost_delete_post? +

Register the Ghost MCP Server MCP server in PolicyLayer and add a rule for ghost_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 Ghost MCP Server. Nothing to install.

What risk level is ghost_delete_post? +

ghost_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 ghost_delete_post? +

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

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

ghost_delete_post is provided by the Ghost MCP Server MCP server (jgardner04/ghost-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ghost MCP Server tool call.

Start from Ghost MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →