# create_block_slot

Create a blocked time slot to prevent bookings during specific times

Agent View of the PolicyLayer registry record for `create_block_slot`. HTML page: https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/create-block-slot

## Facts

- Tool: `create_block_slot`
- Server: GoHighLevel MCP Server (`thinkbedo/gohighlevel_mcp`) — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp.md
- Homepage: https://github.com/ThinkBeDo/gohighlevel_mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why create_block_slot is rated Medium

This tool creates calendar/scheduling entries (blocked time slots) which modify state but can be undone by deleting or modifying the block. It does not execute external commands, delete irreversibly, move money, or retrieve data only.

From the tool's own definition: "Tool name and description indicate it 'Create[s] a blocked time slot' - a reversible data modification operation. The verb 'create' and action of creating/setting scheduling data aligns with Write category operations."

## Use case

AI agents use create_block_slot to create or update resources in GoHighLevel MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GoHighLevel MCP Server environment.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_block_slot": {
      "limits": [
        {
          "counter": "create_block_slot_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on GoHighLevel MCP Server (254)

- `bulk_delete_social_posts` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/bulk-delete-social-posts.md
- `cancel_scheduled_email` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/cancel-scheduled-email.md
- `cancel_scheduled_message` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/cancel-scheduled-message.md
- `delete_appointment` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-appointment.md
- `delete_appointment_note` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-appointment-note.md
- `delete_calendar` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-calendar.md
- `delete_calendar_group` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-calendar-group.md
- `delete_calendar_notification` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-calendar-notification.md
- `delete_calendar_resource_equipment` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-calendar-resource-equipment.md
- `delete_calendar_resource_room` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-calendar-resource-room.md
- `delete_contact` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-contact.md
- `delete_contact_note` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-contact-note.md
- `delete_contact_task` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-contact-task.md
- `delete_conversation` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-conversation.md
- `delete_coupon` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-coupon.md
- `delete_custom_provider_integration` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-custom-provider-integration.md
- `delete_email_template` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-email-template.md
- `delete_invoice_template` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-invoice-template.md
- `delete_location` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-location.md
- `delete_location_custom_field` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-location-custom-field.md
- `delete_location_custom_value` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-location-custom-value.md
- `delete_location_tag` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-location-tag.md
- `delete_location_template` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-location-template.md
- `delete_media_file` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-media-file.md
- `delete_object_record` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-object-record.md
- `delete_opportunity` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-opportunity.md
- `delete_social_account` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-social-account.md
- `delete_social_post` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-social-post.md
- `ghl_delete_association` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/ghl-delete-association.md
- `ghl_delete_custom_field` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/ghl-delete-custom-field.md
- …and 224 more: https://policylayer.com/tools/thinkbedo-gohighlevel-mcp.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=thinkbedo-gohighlevel-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/thinkbedo-gohighlevel-mcp