AI agents call delete-post to permanently remove resources in Bluesky — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of posts is a destructive action that cannot be undone. Once deleted, the post is permanently removed and cannot be recovered. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The severity is high because an AI agent with access to this tool could maliciously delete a user's posts, damaging their online presence and reputation,…
From the tool's definition Tool name is 'delete-post' and description states 'Delete one of your posts' — this irreversibly removes content from the Bluesky platform.
Documented attack patterns abuse exactly the kind of access delete-post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bluesky, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-post:
{
"version": "1",
"default": "deny",
"hide": [
"delete-post"
]
}delete-post disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete one of your posts. It is categorised as a Destructive tool in the Bluesky MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bluesky 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 Bluesky. 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 Bluesky MCP server (semioz/bluesky-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bluesky, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Bluesky tools catalogued and risk-classified — across an index of 43,000+ MCP servers.