# get_blocked_slots

Get blocked time slots for a location

Agent View of the PolicyLayer registry record for `get_blocked_slots`. HTML page: https://policylayer.com/tools/tailormadeweddings-gohighlevel-mcp/get-blocked-slots

## Facts

- Tool: `get_blocked_slots`
- Server: GoHighLevel MCP Server (`tailormadeweddings/gohighlevel-mcp`) — https://policylayer.com/tools/tailormadeweddings-gohighlevel-mcp.md
- Homepage: https://github.com/TailorMadeWeddings/GoHighLevel-MCP
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why get_blocked_slots is rated Low

This tool retrieves and queries existing blocked time slot information. There are no side effects, data modifications, deletions, code execution, or financial transactions. It is a straightforward data retrieval operation consistent with the Read category (fetch, get operations). The severity is low because unauthorized access to scheduling data presents minimal harm compared to other risk categories.

From the tool's own definition: "Tool name 'get_blocked_slots' and description 'Get blocked time slots for a location' both indicate a read-only query operation that retrieves scheduling data without modification."

## Use case

AI agents call get_blocked_slots to retrieve information from GoHighLevel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_blocked_slots": {}
  }
}
```

## Other tools on GoHighLevel MCP Server (261)

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