Delete every draft/scheduled/failed/paused post matching a caller-defined group_id, post_group_id, api_group_id, or release_id. DESTRUCTIVE: inspect the group first, list the affected posts, and pass confirm=true only after explicit confirmation.
AI agents call delete_post_group to permanently remove resources in Posterly — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes posts in bulk based on group identifiers. The description itself identifies it as destructive, and deletion of data cannot be reversed. The severity is high rather than critical because the impact is limited to social media draft/scheduled posts rather than primary business data or financial systems, but the bulk deletion capability and irreversibility warrant the Destructive category…
From the tool's definition Tool description explicitly labels it as 'DESTRUCTIVE' and performs deletion: 'Delete every draft/scheduled/failed/paused post matching a caller-defined group_id, post_group_id, api_group_id, or release_id.' The action cannot be undone and affects multiple…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Delete every draft/scheduled/failed/paused post matching a caller-defined group_id, post_group_id, api_group_id, or release_id. DESTRUCTIVE: inspect the group first, list the affected posts, and pass confirm=true only after explicit confirmation. It is categorised as a Destructive tool in the Posterly MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Posterly MCP server in PolicyLayer and add a rule for delete_post_group: 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 Posterly. Nothing to install.
delete_post_group 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_group 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_group. 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_group is provided by the Posterly MCP server (posterly-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 →