Skip to main content
Book a demo

Connect Microsoft Outlook to Cursor

Give Cursor governed access to Microsoft Outlook’s 37 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cursor setup guide

Set up

Add Microsoft Outlook to Cursor in four steps

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

  1. 1

    Approve Microsoft Outlook in Runlayer

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

  2. 2

    Connect Cursor to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, Microsoft Outlook’s 37 tools show up in Cursor’s own tool list.

    Cursor setup guide
  3. 3

    Sign in to Microsoft Outlook

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

  4. 4

    Use Microsoft Outlook from Cursor

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

Tools

37 Microsoft Outlook tools in Cursor

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

  • Create draft

    Create a new Outlook draft message in the Drafts folder without sending it.

  • Create reply draft

    Create an editable Reply or Reply-All draft attached to an existing Outlook thread.

  • Delete attachment

    Delete an attachment from an Outlook message or draft.

  • Delete message

    Delete a message from an Outlook mailbox.

  • Download attachment

    Download the content of a specific attachment from an Outlook message.

  • Forward message

    Forward an existing Outlook message to one or more recipients.

  • Get attachments

    List all attachments on an Outlook message, returning metadata but not file content.

  • Get message

    Fetch the full content of a single Outlook message by id, headers and body included.

See all 37 Microsoft Outlook tools

Control

What Runlayer can see and stop in Cursor

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

  • Gateway policy (available)

    Every Microsoft Outlook call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cursor 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 Cursor runs it, including calls to MCP servers.

  • Block output after it runs (available)

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

  • Redact output in place (not available)

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

In Cursor

  • Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
  • The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.

Frequently asked questions

Connect more

Find another combination