Skip to main content
Book a demo

Connect Google Forms to Goose

Give Goose governed access to Google Forms’s 6 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Goose setup guide

Set up

Add Google Forms to Goose in four steps

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

  1. 1

    Approve Google Forms in Runlayer

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

  2. 2

    Connect Goose to Runlayer

    Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Google Forms’s 6 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Goose setup guide
  3. 3

    Sign in to Google Forms

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

  4. 4

    Use Google Forms from Goose

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

Tools

6 Google Forms tools in Goose

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

  • Update batch

    Apply a batch of write operations to an existing form, applied in order.

  • Create

    Create a new Google Form.

  • Get

    Get the structure and content of a Google Form using its form ID

  • List

    List your Google Forms.

  • Responses

    Get responses for a Google Form.

  • Search

    Search for Google Forms in your Drive.

Control

What Runlayer can see and stop in Goose

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Goose 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 before Goose runs it.

  • Block output after it runs (available)

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

  • Redact output in place (not available)

    Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination