記事を削除
AI agents call delete_post 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 deletes a post from a Ghost CMS instance, which cannot be undone. Deletion of content is an irreversible destructive action. While the blast radius is primarily limited to content loss (not system-wide or financial), the permanent nature and potential impact on live websites justifies 'high' severity and the Destructive category.
From the tool's definition Tool name 'delete_post' combined with sibling tools including 'delete_member' and 'delete_page' on a Ghost CMS admin server. Description translates to 'delete post' (Japanese: 記事を削除).
Attacks that exploit this kind of access
記事を削除. 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_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.
delete_post 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_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.
Set action: deny in the PolicyLayer policy for 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.
delete_post is provided by the Ghost MCP Server MCP server (mtane0412/ghost-mcp-server). 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 →