AI agents call posts_delete to permanently remove resources in Ghost MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes published content from a Ghost CMS instance. Even though the description is empty, the name combined with the server's purpose (managing posts in a CMS) makes the destructive intent clear. Deletion of CMS content is a permanent action that cannot be undone through the API.
From the tool's definition Tool name 'posts_delete' combined with server context (Ghost CMS content management) indicates irreversible deletion of blog posts. The tool name explicitly contains 'delete', and Ghost posts, once deleted, cannot be recovered without database restoration.
Documented attack patterns abuse exactly the kind of access posts_delete gives an agent:
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 posts_delete:
{
"version": "1",
"default": "deny",
"hide": [
"posts_delete"
]
}posts_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
posts_delete. 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.
Register the Ghost MCP Server MCP server in PolicyLayer and add a rule for posts_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 Ghost MCP Server. Nothing to install.
posts_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the posts_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.
Set action: deny in the PolicyLayer policy for posts_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.
posts_delete is provided by the Ghost MCP Server MCP server (mfydev/ghost-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
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.
Free to start. No card required.
42 Ghost MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.