This record as markdown: /tools/ghl/update-calendar-resource-room.md
What update_calendar_resource_room does on Ghl
AI agents use update_calendar_resource_room 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 | — | Room name |
capacity | number | — | Room capacity |
isActive | boolean | — | Whether resource is active |
quantity | number | — | Total quantity available |
resourceId | string | Yes | Room resource ID |
calendarIds | array | — | Associated calendar IDs |
description | string | — | Room description |
outOfService | number | — | Number currently out of service |
Parameters from the server's own tool schema.
Why update_calendar_resource_room is rated Medium
This tool modifies calendar resource properties but does not delete data or execute arbitrary operations. The impact is scoped to room resource attributes (likely availability, capacity, settings), making it a Write operation. Severity is medium because misconfiguration could disrupt scheduling and resource allocation across the organization, but changes are reversible.
From the tool's definition Tool name 'update_calendar_resource_room' with description 'Update room resource details' indicates modification of existing calendar resource data. The verb 'update' and 'resource_room' context suggest reversible changes to scheduling/room configuration data.
Attacks that exploit this kind of access
The rule that runs update_calendar_resource_room 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 update_calendar_resource_room, this is the rule to start with:
update_calendar_resource_room 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 update_calendar_resource_room call is checked against it from then on.
Questions about update_calendar_resource_room
Update room resource details. 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.
update_calendar_resource_room accepts 8 parameters: name, capacity, isActive, quantity, resourceId, calendarIds, description, outOfService. Required: resourceId. 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 update_calendar_resource_room: 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.
update_calendar_resource_room 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 update_calendar_resource_room 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 update_calendar_resource_room. 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.
update_calendar_resource_room 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