This record as markdown: /tools/ghl/update-block-slot.md
What update_block_slot does on Ghl
AI agents use update_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 | — | Updated title/reason for the block |
endTime | string | — | Updated end time in ISO format |
startTime | string | — | Updated start time in ISO format |
calendarId | string | — | Updated calendar ID for the block |
blockSlotId | string | Yes | The unique ID of the block slot to update |
assignedUserId | string | — | Updated assigned user ID |
Parameters from the server's own tool schema.
Why update_block_slot is rated Medium
This tool creates or modifies calendar blocking data reversibly. It updates (not creates fresh) an existing blocked time slot, which is a data modification operation. The action is reversible—the slot can be updated again or unblocked. While it affects scheduling, it does not execute external operations, delete data irreversibly, or involve financial transactions.
From the tool's definition Tool name 'update_block_slot' and description 'Update an existing blocked time slot' indicate modification of calendar/scheduling data.
Attacks that exploit this kind of access
The rule that runs update_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 update_block_slot, this is the rule to start with:
update_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 update_block_slot call is checked against it from then on.
Questions about update_block_slot
Update an existing blocked time slot. 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.
update_block_slot accepts 6 parameters: title, endTime, startTime, calendarId, blockSlotId, assignedUserId. Required: blockSlotId. 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 update_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.
update_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 update_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 update_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.
update_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