summarize_calendar_availability

Summarize available booking slots across one or more calendars for a date range.

SERVERGoHighLevel MCP Server SOURCEbusybee3333/go-high-level-mcp-2026-complete
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/busybee3333-go-high-level-mcp-2026-complete/summarize-calendar-availability.md

What summarize_calendar_availability does on GoHighLevel MCP Server

AI agents call summarize_calendar_availability to retrieve information from GoHighLevel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why summarize_calendar_availability is rated Low

This tool queries and retrieves calendar availability information. It performs no data modification, deletion, code execution, or financial operations. It is a straightforward read operation that returns calendar slot availability for informational purposes, similar to search or fetch operations. The low severity reflects minimal risk from misuse—an AI agent querying calendar slots poses no substantial harm.

From the tool's definition Tool name 'summarize_calendar_availability' and description 'Summarize available booking slots across one or more calendars for a date range' indicate read-only retrieval of calendar data without modification or side effects.

Questions about summarize_calendar_availability

What does the summarize_calendar_availability tool do? +

Summarize available booking slots across one or more calendars for a date range. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on summarize_calendar_availability? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for summarize_calendar_availability: 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.

What risk level is summarize_calendar_availability? +

summarize_calendar_availability is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit summarize_calendar_availability? +

Yes. Add a rate_limit block to the summarize_calendar_availability 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 summarize_calendar_availability completely? +

Set action: deny in the PolicyLayer policy for summarize_calendar_availability. 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 summarize_calendar_availability? +

summarize_calendar_availability is provided by the GoHighLevel MCP Server MCP server (busybee3333/go-high-level-mcp-2026-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on GoHighLevel MCP Server, and thousands of servers like it.

// 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 GoHighLevel MCP Server'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.