Connect Microsoft SharePoint to Codex
Give Codex governed access to Microsoft SharePoint’s 40 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Microsoft SharePoint to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 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
Connect Codex to Runlayer
Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Microsoft SharePoint’s 40 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).
Codex setup guide - 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
Use Microsoft SharePoint from Codex
Microsoft SharePoint’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
40 Microsoft SharePoint tools in Codex
Runlayer policy decides which of these Codex 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.
Control
What Runlayer can see and stop in Codex
Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.
Gateway policy (available)
Every Microsoft SharePoint call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Codex 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 or permission request before Codex runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Codex’s model sees it.
Redact output in place (not available)
Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
Frequently asked questions
Connect more