create_block_slot

Create a blocked time slot to prevent bookings during specific times

SERVERGhl SOURCEghl-mcp-server
Medium RISK CLASS
Category Write
Parameters 52 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about create_block_slot

What does the create_block_slot tool do? +

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.

What parameters does create_block_slot accept? +

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.

How do I enforce a policy on create_block_slot? +

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.

What risk level is create_block_slot? +

create_block_slot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_block_slot? +

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.

How do I block create_block_slot completely? +

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.

What MCP server provides create_block_slot? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ghl's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.