# bulk_delete_social_posts

Delete multiple social media posts at once (max 50)

Agent View of the PolicyLayer registry record for `bulk_delete_social_posts`. HTML page: https://policylayer.com/tools/keshigami-ghl-mcp-workiong/bulk-delete-social-posts

## Facts

- Tool: `bulk_delete_social_posts`
- Server: GoHighLevel MCP Server (`keshigami/ghl-mcp-workiong`) — https://policylayer.com/tools/keshigami-ghl-mcp-workiong.md
- Homepage: https://github.com/Keshigami/ghl-mcp-workiong
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "bulk_delete_social_posts",
    "arguments": {}
  }
}
```

## Why bulk_delete_social_posts is rated Critical

This tool performs irreversible deletion of social media posts in bulk. Deletion cannot be undone and represents permanent loss of content. The bulk capability (up to 50 posts) increases the blast radius if misused by an AI agent—an erroneous deletion request could eliminate significant content at once.

From the tool's own definition: "Tool name 'bulk_delete_social_posts' explicitly uses 'delete'; description states 'Delete multiple social media posts at once (max 50)'. The verb 'delete' combined with bulk operation on up to 50 items indicates irreversible removal of data."

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents call bulk_delete_social_posts to permanently remove resources in GoHighLevel MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches GoHighLevel MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "bulk_delete_social_posts"
  ]
}
```

## Other tools on GoHighLevel MCP Server (254)

- `cancel_scheduled_email` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/cancel-scheduled-email.md
- `cancel_scheduled_message` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/cancel-scheduled-message.md
- `delete_appointment` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-appointment.md
- `delete_appointment_note` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-appointment-note.md
- `delete_calendar` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-calendar.md
- `delete_calendar_group` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-calendar-group.md
- `delete_calendar_notification` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-calendar-notification.md
- `delete_calendar_resource_equipment` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-calendar-resource-equipment.md
- `delete_calendar_resource_room` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-calendar-resource-room.md
- `delete_contact` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-contact.md
- `delete_contact_note` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-contact-note.md
- `delete_contact_task` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-contact-task.md
- `delete_conversation` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-conversation.md
- `delete_coupon` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-coupon.md
- `delete_custom_provider_integration` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-custom-provider-integration.md
- `delete_email_template` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-email-template.md
- `delete_invoice_template` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-invoice-template.md
- `delete_location` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-location.md
- `delete_location_custom_field` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-location-custom-field.md
- `delete_location_custom_value` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-location-custom-value.md
- `delete_location_tag` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-location-tag.md
- `delete_location_template` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-location-template.md
- `delete_media_file` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-media-file.md
- `delete_object_record` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-object-record.md
- `delete_opportunity` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-opportunity.md
- `delete_social_account` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-social-account.md
- `delete_social_post` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-social-post.md
- `ghl_delete_association` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/ghl-delete-association.md
- `ghl_delete_custom_field` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/ghl-delete-custom-field.md
- `ghl_delete_custom_field_folder` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/ghl-delete-custom-field-folder.md
- …and 224 more: https://policylayer.com/tools/keshigami-ghl-mcp-workiong.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=keshigami-ghl-mcp-workiong · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/keshigami-ghl-mcp-workiong