Skip to main content
Book a demo

Connect Google Calendar to Codex

Give Codex governed access to Google Calendar’s 13 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Codex setup guide

Set up

Add Google Calendar to Codex in four steps

Admins approve the server once. Everyone in Codex then gets it through the same governed connection.

  1. 1

    Approve Google Calendar in Runlayer

    Add Google Calendar from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Codex to Runlayer

    Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Google Calendar’s 13 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).

    Codex setup guide
  3. 3

    Sign in to Google Calendar

    Sign in the way Google Calendar requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Google Calendar from Codex

    Google Calendar’s approved tools appear in Codex. Every call is checked against policy and recorded.

Tools

13 Google Calendar tools in Codex

Runlayer policy decides which of these Codex users can call. 4 read data only and 2 can change or delete data.

  • Create Calendar

    Create a new calendar.

  • Create event

    Create a new event in your Google Calendar with detailed options including attendees, location, reminders, and recurrence rules.

  • Delete Calendar

    Delete a secondary calendar.

  • Delete event

    Delete an event from your calendar.

  • Get event

    Get detailed information about a specific calendar event including title, description, time, location, attendees, and recurrence rules.

  • Get free busy

    Check free/busy information for calendars within a time range.

  • List calendars

    List all calendars accessible to the authenticated user.

  • List events

    List events from your Google Calendar.

See all 13 Google Calendar tools

Control

What Runlayer can see and stop in Codex

Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.

  • Gateway policy (available)

    Every Google Calendar call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Codex as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call or permission request before Codex runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Codex’s model sees it.

  • Redact output in place (not available)

    Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination