disable_calendar_group · GoHighLevel MCP Server MCP

WHAT IT DOES

What disable_calendar_group does on GoHighLevel MCP Server

AI agents use disable_calendar_group 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.

WHY IT NEEDS A POLICY

Why disable_calendar_group needs a policy

The tool changes the operational state of a calendar group but does not delete or destroy data, nor does it execute arbitrary code or move money. It is a write operation because it modifies configuration state. Severity is medium because disabling a calendar group could disrupt calendar functionality and workflows for users relying on that group, but the change is fully reversible (it can be re-enabled).

From the tool's definition Tool description states 'Enable or disable a calendar group' — this modifies the state of a calendar group (toggling its enabled/disabled status), which is a reversible configuration change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disable_calendar_group Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "disable_calendar_group": {
      "limits": [
        {
          "counter": "disable_calendar_group_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GoHighLevel MCP Server, so you can run agents against it safely.

FAQ

Questions about disable_calendar_group

What does the disable_calendar_group tool do? +

Enable or disable a calendar group. 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.

How do I enforce a policy on disable_calendar_group? +

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

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

Can I rate-limit disable_calendar_group? +

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

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

disable_calendar_group is provided by the GoHighLevel MCP Server MCP server (tailormadeweddings/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.