This record as markdown: /tools/ghl/bulk-delete-social-posts.md
What bulk_delete_social_posts does on Ghl
AI agents call bulk_delete_social_posts to permanently remove resources in Ghl, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
postIds | array | Yes | Array of post IDs to delete |
Parameters from the server's own tool schema.
Why bulk_delete_social_posts is rated Critical
This tool permanently removes social media posts without recovery options. The bulk capability (up to 50 posts deleted in a single call) amplifies the risk. An AI agent given insufficient constraints or misinterpreting user intent could delete large volumes of content irreversibly.
From the tool's definition Tool name 'bulk_delete_social_posts' and description 'Delete multiple social media posts at once (max 50)' explicitly indicate irreversible deletion of data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bulk_delete_social_posts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bulk_delete_social_posts, this is the rule to start with:
bulk_delete_social_posts is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every bulk_delete_social_posts call is checked against it from then on.
Questions about bulk_delete_social_posts
Delete multiple social media posts at once (max 50). It is categorised as a Destructive tool in the Ghl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
bulk_delete_social_posts accepts 1 parameter: postIds. Required: postIds. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for bulk_delete_social_posts: 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 Ghl. Nothing to install.
bulk_delete_social_posts 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 bulk_delete_social_posts 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 bulk_delete_social_posts. 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.
bulk_delete_social_posts is provided by the Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
Across the catalogue