Skip to main content
Book a demo

Connect Google Docs to Codex

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

Book a demo Codex setup guide

Set up

Add Google Docs 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 Docs in Runlayer

    Add Google Docs 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 Docs’s 21 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 Docs

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

  4. 4

    Use Google Docs from Codex

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

Tools

21 Google Docs tools in Codex

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

  • Add comment

    Add a comment to a specific text range in a Google Docs document.

  • Apply doc updates

    Apply an ordered batch of raw Google Docs API Request objects to a document via documents.batchUpdate.

  • Create file

    Markdown (recommended, default path): uploaded as text/markdown and converted by Google Drive's native markdown importer (headers, bold, italic, lists, tables, blockquotes, fenced code blocks, links,…

  • Delete between text

    Delete a whole block of a document — a heading and everything beneath it, tables included — by naming the text at each end instead of computing character indices.

  • Delete text

    Delete all occurrences of specific text from a Google Docs document.

  • Edit table

    Structurally edit an existing table in a Google Doc: insert/delete rows and columns, set a column width, style a cell (background color, vertical alignment, padding), replace a cell's text, or…

  • Fetch

    Fetch the content of a Google Docs document using its document ID.

  • Fetch all tabs

    Fetch content from all tabs in a Google Docs document.

See all 21 Google Docs 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 Docs 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