Supprime un post
AI agents call delete_post to permanently remove resources in Blogger MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The delete_post tool permanently removes published or draft content from Google Blogger. This is an irreversible action with no undo capability—once deleted, the post and its associated metadata are lost. An AI agent with access to this tool could maliciously or erroneously delete valuable blog content, damage a user's online presence, or cause loss of published information.
From the tool's definition Tool name is 'delete_post' and description translates to 'Deletes a post'. This irreversibly removes a blog post from the Blogger platform.
Attacks that exploit this kind of access
Supprime un post. It is categorised as a Destructive tool in the Blogger MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Blogger 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 Blogger 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 Blogger MCP Server MCP server (niyonabil/blogger-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 →