Plugin governance
How a workspace controls which plugin tools its agents can request, where plugin credentials live, and how the audit record and role requirements work.
Oxagen plugins add external tools and first-party capabilities that an agent can request. Every plugin install is workspace-scoped. A plugin installed in one workspace is not visible to any other workspace, which gives security and compliance teams a narrow control surface.
Workspace-scoped plugin model
Workspace A → plugins installed here are available only in Workspace A
Workspace B → independent plugin list; no visibility into Workspace A's plugins
Workspace C → ...Org Owners and Admins can install plugins from the marketplace into any workspace they belong to. Workspace Owners and Admins can install plugins into their own workspace. Every install, connection, and enable or disable action applies to one workspace.
Installing plugins
Use browse_plugin_catalog and get_catalog_plugin to inspect a plugin. Call install_plugin to install it in the workspace.
An authenticated connection is a separate step. Use reauth_plugin_credential for OAuth or set_plugin_secret for a secret. See Workspace plugins.
Enable and disable
One capability, set_plugin_enabled, turns a plugin on and off. For an MCP server or integration plugin, it turns the workspace's MCP server connection on or off. That connection holds the server's address, sign-in settings and on/off state. For a capability pack, it turns the pack on or off.
A disabled plugin's tools leave every agent's tool list. For an MCP server, disabling also blocks reconnection until you enable it again.
Credential security
The credential a plugin needs stays in Oxagen, held by the workspace. The agent never sees it. Oxagen encrypts OAuth tokens and API keys at rest with AES-256-GCM. If an OAuth token expires or is revoked, org managers get an in-app notification, and someone must authenticate again before the plugin's tools come back.
Uninstalling
Call uninstall_plugin for the workspace installation. Existing tool-call audit records remain. Uninstalling a plugin is separate from deleting data it previously produced.
The record
Oxagen records plugin governance actions in security.security_events (Postgres):
| Event | When it fires |
|---|---|
plugin.installed | Plugin installed into a workspace. |
plugin.uninstalled | Plugin uninstalled from a workspace. |
plugin.enabled_changed | Plugin listing enabled or disabled, or a workspace MCP server connection activated or deactivated (set_plugin_enabled). |
plugin.credential_set | A plugin credential stored. |
plugin.credential_revoked | A plugin credential revoked. |
plugin.denylist_added | Reserved name. There is no plugin denylist, so nothing emits it. |
plugin.denylist_removed | Reserved name. There is no plugin denylist, so nothing emits it. |
Role requirements
| Action | Required role |
|---|---|
| Browse marketplace | Any workspace member |
| Install or uninstall a plugin | Workspace Owner, Workspace Admin, or Org Owner/Admin |
| Connect OAuth or set API key | Org Owner or Org Admin only |
| Add custom MCP server or registry | Workspace Owner or Org Owner/Admin |
| Enable or disable a plugin | Workspace Owner or Org Owner/Admin |
For more information, see the Plugin marketplace and Workspace plugins guides.