Create Google Calendar events for a hotel or Airbnb stay. Creates 3 events: a multi-day all-day event, a timed check-in event, and a timed check-out event. Provide extracted details from a booking confirmation.
AI agents use create_lodging_event to create or update resources in Gcal — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gcal environment.
This tool creates new calendar entries, which is a reversible write operation. It modifies the user's Google Calendar by adding events but does not delete, execute arbitrary code, move money, or perform irreversible actions. The severity is medium because calendar pollution or incorrect entries could disrupt scheduling, but the effects are easily corrected by deleting the created events.
From the tool's definition Tool description states it "Create[s] Google Calendar events" - specifically creating three calendar events (multi-day all-day event, check-in event, check-out event) based on booking confirmation details.
Attacks that exploit this kind of access
Create Google Calendar events for a hotel or Airbnb stay. Creates 3 events: a multi-day all-day event, a timed check-in event, and a timed check-out event. Provide extracted details from a booking confirmation. It is categorised as a Write tool in the Gcal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gcal MCP server in PolicyLayer and add a rule for create_lodging_event: 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 Gcal. Nothing to install.
create_lodging_event 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_lodging_event 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_lodging_event. 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_lodging_event is provided by the Gcal MCP server (kwikkid/gcalcli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →