删除指定的博客文章（不可撤销）
AI agents call delete_post to permanently remove resources in Hexo Blog 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 blog posts without the ability to recover them. It matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The severity is high because deletion of blog content represents significant data loss, though the blast radius is limited to the blog domain rather than critical infrastructure.
From the tool's definition Tool name 'delete_post' combined with description '删除指定的博客文章（不可撤销）' which translates to 'Delete specified blog article (irreversible)'. The explicit mention of '不可撤销' (irreversible/cannot be undone) confirms this is a destructive operation.
Attacks that exploit this kind of access
删除指定的博客文章（不可撤销）. It is categorised as a Destructive tool in the Hexo Blog MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hexo Blog 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 Hexo Blog 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 Hexo Blog MCP Server MCP server (leejersey/hexo-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 →