create_block_slot
Create a blocked time slot to prevent bookings during specific times
This record as markdown: /tools/ghl/create-block-slot.md
What create_block_slot does on Ghl
AI agents use create_block_slot to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | — | Title/reason for the block (e.g., "Lunch Break", "Meeting") |
endTime | string | Yes | End time of the block in ISO format (e.g., "2024-01-15T12:00:00-05:00") |
startTime | string | Yes | Start time of the block in ISO format (e.g., "2024-01-15T10:00:00-05:00") |
calendarId | string | — | Specific calendar to block (optional, blocks all if not specified) |
assignedUserId | string | — | User ID to apply the block for |
Parameters from the server's own tool schema.
Why create_block_slot is rated Medium
This falls under Write rather than Execute because it creates a calendar resource (a blocked slot) with predictable, reversible effects. While it affects availability, it doesn't execute arbitrary commands or permanently delete data.
From the tool's definition The tool creates a 'blocked time slot' — a new calendar/scheduling resource that prevents bookings during specified times. This is a write operation that creates/modifies scheduling data.
Attacks that exploit this kind of access
The rule that runs create_block_slot 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 create_block_slot, this is the rule to start with:
create_block_slot stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_block_slot call is checked against it from then on.
Questions about create_block_slot
Create a blocked time slot to prevent bookings during specific times. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_block_slot accepts 5 parameters: title, endTime, startTime, calendarId, assignedUserId. 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 create_block_slot: 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.
create_block_slot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_block_slot 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 create_block_slot. 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.
create_block_slot 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