This record as markdown: /tools/ghl/get-calendar-resource-room.md
What get_calendar_resource_room does on Ghl
AI agents call get_calendar_resource_room to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
resourceId | string | Yes | Room resource ID |
Parameters from the server's own tool schema.
Why get_calendar_resource_room is rated Low
This tool retrieves (gets) information about calendar room resources. The verb 'get' and the passive framing 'Get...details' confirm it is a read-only operation that queries existing data without side effects. No data is created, modified, deleted, or financial operations occur. Severity is low because unauthorized access to room resource metadata poses minimal risk.
From the tool's definition Tool name 'get_calendar_resource_room' and description 'Get specific room resource details' indicate a retrieval operation with no modification of data.
Attacks that exploit this kind of access
The rule that runs get_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 get_calendar_resource_room, this is the rule to start with:
get_calendar_resource_room is read-only, so it stays allowed. 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 get_calendar_resource_room call is checked against it from then on.
Questions about get_calendar_resource_room
Get specific room resource details. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_calendar_resource_room accepts 1 parameter: resourceId. 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 get_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.
get_calendar_resource_room is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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