get_blocked_slots

What get_blocked_slots does on GoHighLevel MCP Server

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.

Why get_blocked_slots is rated Low

This tool retrieves or queries blocked time slot information for scheduling purposes with no side effects, data modification, or external operation triggering. It falls squarely into the Read category. Severity is low because exposure of blocked time slots has minimal security impact—this is typically non-sensitive scheduling metadata used for calendar availability.

From the tool's definition Tool name 'get_blocked_slots' and description 'Get blocked time slots for a location' indicate a retrieval operation. The verb 'Get' and the absence of any modification language confirm this is a read-only query of existing calendar/scheduling data.

The rule that runs get_blocked_slots safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_blocked_slots, this is the rule to start with:

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

Questions about get_blocked_slots