Documentation

Using FGAC with your agent

FGAC.ai is a permission layer between AI agents and your Google account. Agents connect once over MCP; every Gmail, Sheets, and Docs request they make is checked against rules you control — deny by default, allow on your terms.

Not connected yet? Follow the three-step setup guide. See also: multiple Gmail accounts · Google Sheets agents

Example prompts

What to say to Claude (or any MCP agent), and what to expect — including what a denial looks like.

“Summarize my unread email.”

Claude lists and reads recent unread messages and summarizes them. Any message blocked by your rules (a blacklisted label, or content matching a block pattern like a 2FA code) is withheld — Claude sees an “Access restricted” notice instead of the message.

“Read the latest message from my bank.”shows a denial

If your rules block financial mail (by label or content pattern), Claude receives “🚫 Access restricted: Content blocked by rule …” and tells you it can't read that message. The denial names the rule so you know which grant to change if you actually wanted access.

“Email alex@example.com a short status update.”

If alex@example.com matches your send whitelist, the mail is sent and Claude confirms with the Gmail message id. If not, nothing is sent — Claude is told the recipient isn't whitelisted and to ask you to add it in the dashboard.

“What's in the Budget tab of my planning spreadsheet?”

Claude reads the exposed spreadsheet and reports the cell values. Spreadsheets you haven't exposed on the agent's profile are denied by default — Claude is told the sheet isn't exposed rather than seeing any data.

“Log today's totals as a new row in the tracking sheet.”

With Read & Write enabled on that spreadsheet, Claude appends the row and confirms the updated range. If the sheet is read-only, the write is refused with a clear read-only message and no data changes.

“Append today's meeting notes to my running notes doc.”

Google Docs work like Sheets: expose a document in the picker, and with Read & Write enabled Claude appends the notes and confirms. Documents you haven't exposed are denied by default, and a denial includes a one-click approval link so granting access takes seconds.

Tool reference

Read-only tools can run without per-call confirmation in Claude; write tools always ask first. Every tool is additionally checked against your FGAC rules on our servers.

Read-only tools

  • list_accountsLists the inboxes this connection can reach
  • gmail_listLists recent messages, with optional Gmail search query
  • gmail_readReads one message: headers, body text, attachment list
  • gmail_get_attachmentDownloads an attachment (up to ~150 KB)
  • gmail_labelsLists the account's Gmail labels
  • sheets_get_spreadsheetSpreadsheet metadata and sheet tabs
  • sheets_read_rangeReads cell values from a range
  • docs_read_documentReads a Google Doc (optionally trimmed by a field mask)
  • comments_readLists the comments and replies on a doc or sheet
  • get_my_permissionsShows the rules that govern this connection
  • google_api_getAny Google API read endpoint, rule-checked (others limited by your Google grant)
  • request_accessAsks you to approve a specific permission upgrade

Write tools

  • gmail_sendSends mail — recipients must be on your send whitelist
  • sheets_update_rangeOverwrites cells — needs Read & Write on the sheet
  • sheets_append_rowsAppends rows — needs Read & Write on the sheet
  • docs_editEdits a doc via Docs batchUpdate (text, tables, styles) — needs Read & Write
  • sheets_editFormats/restructures a sheet via Sheets batchUpdate — needs Read & Write
  • comments_addAdds a comment or reply on a doc or sheet — needs Read & Write
  • google_api_modifyWrite endpoints incl. Docs/Sheets batchUpdate and file creation, rule-checked

google_api_get and google_api_modify cover the long tail of the Gmail API and Sheets API without loosening anything: raw reads pass the same read rules, the only raw Gmail write is send (whitelist-checked), Sheets and Docs writes (including batchUpdate and file creation) need the same Read & Write grants, and endpoints outside those services are bounded by the narrow Google OAuth scopes FGAC holds.

Limitations

Most of these are safety guarantees, not gaps.

  • Gmail, Google Sheets, and Google Docs are the enforced services. Requests to other Google services are limited by the narrow OAuth scopes FGAC holds — Drive access, for example, covers only files you picked or the agent created (drive.file), and services like Calendar or Slides fail at Google without a granted scope. Rule enforcement arrives service by service.
  • Agents can never delete. No tool exposes DELETE. Trash, empty-trash, and destructive Gmail settings are refused regardless of your rules.
  • Sending requires a whitelist. With no send-whitelist rule configured, all outbound mail is refused. That's the default. When a send is denied, you get a one-click, single-use link to approve exactly that recipient — or the agent can ask via request_access.
  • New connections start read-only. Connecting attaches the agent to your Default Profile: it can read this account's mail — plus any inbox its owner has delegated to you — and nothing else: no sending, no Sheets or Docs, no undelegated inboxes. You can review, re-scope, or block it from the dashboard at any time.
  • Attachments cap at ~150 KB through MCP responses. Larger files must be fetched from Gmail directly.
  • Delegated inboxes need an explicit delegation created by the inbox owner from their own FGAC account, revocable any time. Once granted, the inbox attaches to your Default Profile automatically.

Support

Questions, bug reports, or access issues — email support@fgac.ai. See also the Privacy Policy and Terms of Service.

Get connected