create-calendar-resource
Create calendar resource by resource type
This record as markdown: /tools/drausal-gohighlevel-mcp/create-calendar-resource.md
What create-calendar-resource does on GoHighLevel MCP Server
AI agents use create-calendar-resource 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 create-calendar-resource is rated Medium
The tool performs resource creation which falls under Write category—it creates new data that can be modified or deleted later. The severity is low because calendar resource creation in a CRM platform has minimal blast radius; misuse would only create unwanted calendar entries that can be easily removed. No irreversible data loss, code execution, or financial transactions are involved.
From the tool's definition Tool name explicitly states 'create-calendar-resource', and the description indicates creation of calendar resources. This is a write operation that creates new data (a calendar resource) reversibly, without permanent deletion or financial impact.
Attacks that exploit this kind of access
The rule that runs create-calendar-resource safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create-calendar-resource, this is the rule to start with:
create-calendar-resource 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 GoHighLevel MCP Server, apply this rule, and every create-calendar-resource call is checked against it from then on.
Questions about create-calendar-resource
Create calendar resource by resource type. 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-calendar-resource: 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-calendar-resource 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-calendar-resource 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-calendar-resource. 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-calendar-resource is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). 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.
This server
Across the catalogue