Skip to main content
Book a demo

Connect Microsoft Word to Goose

Give Goose governed access to Microsoft Word’s 4 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Goose setup guide

Set up

Add Microsoft Word to Goose in four steps

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

  1. 1

    Approve Microsoft Word in Runlayer

    Add Microsoft Word 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 Microsoft Word’s 4 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Goose setup guide
  3. 3

    Sign in to Microsoft Word

    Each user signs in to Microsoft Word with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Microsoft Word from Goose

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

Tools

4 Microsoft Word tools in Goose

Runlayer policy decides which of these Goose users can call.

  • Add comment

    Add a new comment in the Word document.

  • Create document

    Create a new Word document in the root of the user's OneDrive.

  • Get document content

    Fetch the raw Word document (DOCX) content from OneDrive/SharePoint given its SharePoint sharing URL.

  • Reply to comment

    Reply to a comment in the Word document.

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 Microsoft Word 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