This record as markdown: /tools/ghl/get-blocked-slots.md
What get_blocked_slots does on Ghl
AI agents call get_blocked_slots to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
userId | string | — | Filter by user ID |
endTime | string | Yes | End time for the query range |
groupId | string | — | Filter by group ID |
startTime | string | Yes | Start time for the query range |
calendarId | string | — | Filter by calendar ID |
Parameters from the server's own tool schema.
Why get_blocked_slots is rated Low
This tool queries and returns blocked time slot data for a location without modifying, deleting, or executing external operations. It is a straightforward read operation typical of scheduling systems. The low severity reflects minimal blast radius—retrieving scheduling information poses no direct risk even if misused by an agent.
From the tool's definition Tool name 'get_blocked_slots' and description 'Get blocked time slots for a location' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_blocked_slots 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 get_blocked_slots, this is the rule to start with:
get_blocked_slots is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every get_blocked_slots call is checked against it from then on.
Questions about get_blocked_slots
Get blocked time slots for a location. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_blocked_slots accepts 5 parameters: userId, endTime, groupId, startTime, calendarId. Required: endTime, startTime. 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 get_blocked_slots: 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.
get_blocked_slots is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_blocked_slots 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 get_blocked_slots. 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.
get_blocked_slots 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.
This server
Across the catalogue