Skip to main content
Book a demo

Connect Microsoft SharePoint to VS Code

Give VS Code governed access to Microsoft SharePoint’s 40 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo VS Code setup guide

Set up

Add Microsoft SharePoint to VS Code in four steps

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

  1. 1

    Approve Microsoft SharePoint in Runlayer

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

  2. 2

    Connect VS Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Microsoft SharePoint’s 40 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code setup guide
  3. 3

    Sign in to Microsoft SharePoint

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

  4. 4

    Use Microsoft SharePoint from VS Code

    Microsoft SharePoint’s approved tools appear in VS Code. Every call is checked against policy and recorded.

Tools

40 Microsoft SharePoint tools in VS Code

Runlayer policy decides which of these VS Code users can call. 9 read data only and 1 can change or delete data.

  • Create list item

    Create a new item in a SharePoint list.

  • Delete list item

    Delete an item from a SharePoint list.

  • Get list item

    Fetch a single item from a SharePoint list by its id.

  • Get site

    Fetch a single SharePoint site's metadata.

  • List drives

    List the document libraries (drives) in a SharePoint site.

  • List folder items

    List files and folders inside a SharePoint document library folder.

  • List list items

    List items in a SharePoint list.

  • List lists

    List SharePoint lists in a site.

See all 40 Microsoft SharePoint tools

Control

What Runlayer can see and stop in VS Code

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

  • Gateway policy (available)

    Every Microsoft SharePoint call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

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

  • Block output after it runs (available)

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

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination