Create a blocked time slot to prevent bookings during specific times
AI agents use create_block_slot to create or update resources in GoHighLevel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GoHighLevel MCP Server environment.
This tool creates a new resource (a block slot) that modifies the scheduling system state. It is reversible—blocked slots can typically be deleted or modified later. This qualifies as Write rather than Execute because it creates data rather than triggering arbitrary operations.
From the tool's definition Tool name 'create_block_slot' and description 'Create a blocked time slot to prevent bookings during specific times' indicate the tool creates a new calendar/scheduling entry.
Attacks that exploit this kind of access
Create a blocked time slot to prevent bookings during specific times. It is categorised as a Write tool in the GoHighLevel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. 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 GoHighLevel MCP Server MCP server (keshigami/ghl-mcp-workiong). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →