create_out_of_office

SERVERMcp Google Calendar SOURCE@a1-x-tech/mcp-google-calendar

Medium RISK CLASS

Category Write

Parameters 82 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/a1-x-tech-mcp-google-calendar/create-out-of-office.md

WHAT IT DOES

What create_out_of_office does on Mcp Google Calendar

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.

Parameter	Type	Required	Description
`summary`	string	—	Title (defaults to "Out of office").
`time_zone`	string	—	IANA time zone name, e.g. "Europe/Berlin" or "America/New_York".
`calendar_id`	string	—	The calendar id from list_calendars, or "primary" for the authenticated user's main calendar.
`auto_decline`	string	—	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	—	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	—	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.

RISK

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_out_of_office safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Calendar, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_out_of_office, this is the rule to start with:

create_out_of_office Rate-limited

create_out_of_office 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_out_of_office": {
      "limits": [
        {
          "counter": "create_out_of_office_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Google Calendar, apply this rule, and every create_out_of_office call is checked against it from then on.

FAQ

Questions about create_out_of_office

What does the create_out_of_office tool do? +

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. It is categorised as a Write tool in the Mcp Google Calendar MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does create_out_of_office accept? +

create_out_of_office accepts 8 parameters: summary, time_zone, calendar_id, auto_decline, send_updates, end_date_time, decline_message, start_date_time. Required: end_date_time, start_date_time. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_out_of_office? +

Register the Mcp Google Calendar MCP server in PolicyLayer and add a rule for create_out_of_office: 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 Mcp Google Calendar. Nothing to install.

What risk level is create_out_of_office? +

create_out_of_office is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_out_of_office? +

Yes. Add a rate_limit block to the create_out_of_office 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.

How do I block create_out_of_office completely? +

Set action: deny in the PolicyLayer policy for create_out_of_office. 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.

What MCP server provides create_out_of_office? +

create_out_of_office is provided by the Mcp Google Calendar MCP server (@a1-x-tech/mcp-google-calendar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Google Calendar, and thousands of servers like it.

This server

All 19 Mcp Google Calendar tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →