Deletes a tag from Ghost blog
AI agents call delete_ghost_tag 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 permanently removes data (a tag) from the Ghost blog system without the ability to undo the action through the tool itself. Deletion is irreversible and constitutes a destructive operation. Severity is high rather than critical because the blast radius is limited to tag metadata rather than core content or financial systems; however, bulk tag deletion could disrupt blog organization and SEO structure.
From the tool's definition Tool name contains 'delete' and description states 'Deletes a tag from Ghost blog'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Deletes a tag from Ghost blog. 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 delete_ghost_tag: 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.
delete_ghost_tag 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 delete_ghost_tag 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 delete_ghost_tag. 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.
delete_ghost_tag is provided by the Ghost MCP Server MCP server (oculairmedia/ghost-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →