MCP Server Governance & Outbound Action Controls
Admins can govern inbound MCP server exposure and outbound MCP action destinations before users connect external tools.
Screenshots
These screenshots come from the same app-side Latest Features gallery used in the product experience.
Current release version for MCP Server Governance & Outbound Action Controls: 0.261.001
SimpleChat can operate as a governed inbound MCP server exposing conversations, documents, prompts, tags, and workflow tools to MCP clients. Outbound MCP actions add presets, server-side preconfiguration catalogs, destination governance, Test Connection support, observability controls, Application Insights KQL starters, and standards-compliant tool argument normalization for end users invoking MCP actions.
Why It Matters
This matters because admins can unlock MCP interoperability while controlling destinations, observability, and supported tool surfaces.
How to Try It
- Open Admin Settings > Agents and review outbound MCP action configuration and available presets.
- Open Admin Settings > Inbound MCP to enable the inbound server and scope it with required roles, scope, and client or tenant allow-lists.
- Open Admin Settings > MCP Governance and apply destination or capability policies before making MCP actions broadly available.
- Use Test Connection on configured MCP actions so users see reliable action availability.
- Tell users which MCP clients or outbound destinations are approved before enabling the capability tenant-wide.
Where to Find It
- Open Agents — Configure outbound MCP action presets and server-side catalogs.
- Open Inbound MCP — Enable and scope the inbound MCP server exposed to MCP clients.
- Open MCP Governance — Control MCP destination and capability access.
- Open Logging — Review observability and KQL starter guidance for MCP operations.