Connect Microsoft Word to OpenCode
Give OpenCode governed access to Microsoft Word’s 4 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Microsoft Word to OpenCode in four steps
Admins approve the server once. Everyone in OpenCode then gets it through the same governed connection.
- 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
Connect OpenCode to Runlayer
Users add the Runlayer Plugin to OpenCode by hand using Runlayer’s generic MCP steps. OpenCode reaches Microsoft Word’s 4 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
OpenCode setup guide - 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
Use Microsoft Word from OpenCode
Microsoft Word’s approved tools appear in OpenCode. Every call is checked against policy and recorded.
Tools
4 Microsoft Word tools in OpenCode
Runlayer policy decides which of these OpenCode 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 OpenCode
Some controls apply to every client at the gateway. Others depend on what OpenCode exposes to Runlayer.
Gateway policy (available)
Every Microsoft Word call from OpenCode passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, OpenCode as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for OpenCode yet, so control happens at the gateway.
Frequently asked questions
Connect more