create_calendar_resource_equipment
Create a calendar equipment resource
This record as markdown: /tools/ghl/create-calendar-resource-equipment.md
What create_calendar_resource_equipment does on Ghl
AI agents use create_calendar_resource_equipment 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 |
|---|---|---|---|
name | string | Yes | Equipment name |
capacity | number | Yes | Capacity per unit |
quantity | number | Yes | Total quantity available |
calendarIds | array | Yes | Associated calendar IDs |
description | string | Yes | Equipment description |
outOfService | number | Yes | Number currently out of service |
Parameters from the server's own tool schema.
Why create_calendar_resource_equipment is rated Medium
Creating a calendar equipment resource is a reversible write operation that adds new data to the system. It does not execute arbitrary code, delete data irreversibly, move money, or retrieve information. The severity is medium because misconfiguration could create conflicting or unwanted equipment resources, but the impact is limited to calendar management and reversible through deletion.
From the tool's definition Tool name explicitly states 'create' and description states 'Create a calendar equipment resource'. This operation creates new data (equipment resource) in the calendar system.
Attacks that exploit this kind of access
The rule that runs create_calendar_resource_equipment 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 create_calendar_resource_equipment, this is the rule to start with:
create_calendar_resource_equipment 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 create_calendar_resource_equipment call is checked against it from then on.
Questions about create_calendar_resource_equipment
Create a calendar equipment resource. 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.
create_calendar_resource_equipment accepts 6 parameters: name, capacity, quantity, calendarIds, description, outOfService. Required: name, capacity, quantity, calendarIds, description, outOfService. 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 create_calendar_resource_equipment: 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.
create_calendar_resource_equipment 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_equipment 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_equipment. 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_equipment 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