Delete a tag by ID.
AI agents call ghost_delete_tag to permanently remove resources in Ghost CMS MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool deletes tags from a Ghost CMS instance. Tag deletion is an irreversible operation that cannot be undone through normal means. While the blast radius is limited compared to deleting posts or pages (fewer dependent entities typically), deletion operations are categorized as Destructive per the classification rules.
From the tool's definition Tool name 'ghost_delete_tag' with description 'Delete a tag by ID' explicitly performs tag deletion, which is irreversible data removal.
Attacks that exploit this kind of access
Delete a tag by ID. It is categorised as a Destructive tool in the Ghost CMS MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ghost CMS MCP server in PolicyLayer and add a rule for ghost_delete_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 CMS MCP. Nothing to install.
ghost_delete_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 ghost_delete_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 ghost_delete_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.
ghost_delete_tag is provided by the Ghost CMS MCP server (matveev-pavel/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 →