Create
Provisioning on Control Hub
Use the Webex Control Hub to provision Agentic Apps for your organization. This includes configuring user access and authentication, and defining governance controls to manage which agentic capabilities are available to organizational users.
Users acknowledge and agree that they bear full responsibility for understanding, complying with, and managing all aspects of the liability framework related to their use of MCP applications.
This guide is for administrators only. This includes configuring user access and authentication, and defining governance controls to manage which agentic capabilities are available to organizational users.
anchorAccessing your Agentic Apps
anchorIn Control Hub, go to Apps → Agentic Apps.
This page lists all public Agentic Apps along with the private apps which have been onboarded by users belonging to your organization.
anchorAuthorization
anchorAfter selecting an app from the list, from the General tab, you can configure the app to be allowed or blocked for all users of your organization.
anchorAuthentication
anchorThe Authentication section asks users for details according to the configuration set in the Developer Portal. Supported methods:
| Method | What to provide |
|---|---|
| OAuth 2.0 – Client Credentials | Client ID, Client Secret, Authorization Server URL, Token Endpoint Auth Method, Scope |
| OAuth 2.0 – Authorization Code | Client ID, Client Secret, Registration Endpoint, Authorization Endpoint, Authorization Server URL, Token Endpoint Auth Method, Scope |
| User Token | No input required |
| API Key | The API key |
| Custom Headers | Up to five (5) key–value pairs |
For OAuth 2.0 – Client Credentials, the Token Endpoint Auth Method can be client_secret_basic or client_secret_post. For OAuth 2.0 – Authorization Code, it can be none, client_secret_basic, or client_secret_post.
Custom Headers are configurable for all authentication types.
anchorCapabilities Configuration
anchorFor MCP Servers, you will see three tabs - one for Tools, one for Resources and one for Prompts.
In the Tools section you can do the following:
- Enable/Disable individual tools
- Toggle "Allow signature change" for individual tools - this allows/denies client access in the case of a signature change
- Review details of individual tools - you can check the input, output schemas and annotations of tools
Similar functionalities are available in the Resources and Prompts pages.