# create_out_of_office Creates an Out of Office event that can auto-decline meeting invitations while it lasts (auto_decline: all overlapping meetings, or only new invitations; decline_message customizes the reply). ONLY works on the PRIMARY calendar of a Google Workspace account — consumer Gmail and secondary calendars get HTTP 400. Always timed (start/end date_time), never all-day. Manage it afterwards like any event: update_event to change it, delete_event to remove it, list_events with event_types=["out_of_office"] to find existing blocks. Not retried after an ambiguous failure — check list_events before re-sending. Agent View of the PolicyLayer registry record for `create_out_of_office`. HTML page: https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/create-out-of-office ## Facts - Tool: `create_out_of_office` - Server: Mcp Google Calendar (`@a1-x-tech/mcp-google-calendar`) — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar.md - Install: `npx -y @a1-x-tech/mcp-google-calendar` - Homepage: https://github.com/A1-x-Tech/mcp-google-calendar - Risk category: Write (Medium risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 8 (2 required) - Recommended policy verdict: Rate-limited ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `summary` | string | no | Title (defaults to "Out of office"). | | `time_zone` | string | no | IANA time zone name, e.g. "Europe/Berlin" or "America/New_York". | | `calendar_id` | string | no | The calendar id from list_calendars, or "primary" for the authenticated user's main calendar. | | `auto_decline` | string | no | Which conflicting meeting invitations Calendar auto-declines: none, all overlapping ones, or only new ones arriving after the block is created (existing meeting | | `send_updates` | string | no | Who receives an email about this change: all guests, only guests outside your organization, or nobody. Defaults to none — attendees are NOT notified unless you | | `end_date_time` | string | yes | Block end, RFC3339. | | `decline_message` | string | no | Message sent with each auto-declined invitation. | | `start_date_time` | string | yes | Block start, RFC3339 (these blocks are always timed, never all-day). | Parameters from the server's own tool schema. ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "create_out_of_office", "arguments": { "end_date_time": "", "start_date_time": "" } } } ``` ## Why create_out_of_office is rated Medium An AI agent can call create_out_of_office faster than any human can review: one bad instruction and it creates or modifies resources in Mcp Google Calendar by the hundred, each call as confident as the last. ## Use case AI agents use create_out_of_office to create or update resources in Mcp Google Calendar, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Google Calendar environment. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Google Calendar: ```json { "version": "1", "default": "deny", "tools": { "create_out_of_office": { "limits": [ { "counter": "create_out_of_office_rate", "window": "minute", "max": 30, "scope": "grant" } ] } } } ``` ## Other tools on Mcp Google Calendar (18) - `delete_event` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/delete-event.md - `logout` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/logout.md - `start_login` — Execute — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/start-login.md - `auth_status` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/auth-status.md - `get_calendar` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/get-calendar.md - `get_event` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/get-event.md - `list_calendars` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/list-calendars.md - `list_event_instances` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/list-event-instances.md - `list_events` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/list-events.md - `query_free_busy` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/query-free-busy.md - `raw_request` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/raw-request.md - `create_event` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/create-event.md - `create_focus_time` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/create-focus-time.md - `finish_login` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/finish-login.md - `move_event` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/move-event.md - `set_client` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/set-client.md - `setup_instructions` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/setup-instructions.md - `update_event` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/update-event.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=a1-x-tech-mcp-google-calendar · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/a1-x-tech-mcp-google-calendar