It creates and invites people after the query, exceeding the stated read-only discovery purpose
Source references: 4The description promises to query availability to find a slot, but the final step invokes `calendar +insert` to create a “Meeting” and add two attendees. It does not require presenting the final time, confirming the organizer calendar, or obtaining approval before the write.
If an agent executes the whole recipe automatically, it could create an event in the wrong account or at the wrong time and send or trigger invitations, changing calendars and notifications for the user and attendees.
The source supports this risk. The stated purpose is to query availability and find a meeting slot, but the procedure also directs the agent to call `calendar +insert` and add two example attendees. If the full recipe is followed, it modifies the user's calendar and may send invitations; no pre-write confirmation appears in the steps. A user can ask the author to make creation explicitly optional and restrict execution until the proposed time, organizer calendar, and attendees are shown and approved.
name: recipe-find-free-timedescription: "Query Google Calendar free/busy status for multiple users to find a meeting slot."metadata:Show 3 other places
Query Google Calendar free/busy status for multiple users to find a meeting slot.2. Review the output to find overlapping free slots3. Create event in the free slot: `gws calendar +insert --summary 'Meeting' --attendee user1@company.com --attendee user2@company.com --start '2024-03-18T14:00:00' --end '2024-03-18T14:30:00'`1. Query free/busy: `gws calendar freebusy query --json '{"timeMin": "2024-03-18T08:00:00Z", "timeMax": "2024-03-18T18:00:00Z", "items": [{"id": "user1@company.com"}, {"id": "user2@company.com"}]}'`2. Review the output to find overlapping free slots3. Create event in the free slot: `gws calendar +insert --summary 'Meeting' --attendee user1@company.com --attendee user2@company.com --start '2024-03-18T14:00:00' --end '2024-03-18T14:30:00'`