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.

## Accessing your Agentic Apps In Control Hub, go to **Apps → Agentic Apps**. ![Control Hub Apps Page]()
This page lists all public Agentic Apps along with the private apps which have been onboarded by users belonging to your organization. ![Control Hub Agentic Apps Page]()
## General After 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. ![Agentic App General Page]()
Authorize automatic server data updates - When enabled, updates to the server's name, description, URL (within the same domain), transport type, or other metadata do not require re-authorization before they take effect. However, the admin will see an indication that changes have occurred and can re-authorize at their discretion. ## Authentication

Cisco official servers are automatically configured. You should update the authentication settings mentioned below only if you need to change the default authentication.

The **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`.

![Agentic App Auth Page]()

Custom Headers are configurable for all authentication types.

## Capabilities Configuration For MCP Servers, you will see three tabs - one for **Tools**, one for **Resources** and one for **Prompts**. ![Agentic App Tools Page]()
### Tools In the Tools section you can do the following: 1. **Enable tool:** When a tool is enabled by the org admin, it becomes available to users on the client side. Users can discover and use the tool based on the access configured by the admin. 2. **Disable tool:** When a tool is disabled by the org admin, it is no longer visible or available to users on the client side. This allows admins to restrict access to tools that should not be used within the organization. 3. **Signature change:** When enabled, tools remain accessible to users even if the tool's schema changes after authorization. Org admins do not need to re-authorize each tool when its schema is updated by the developer. However, an indication is shown that the tool signature has drifted from what was originally approved. 4. **Review individual tool details:** Admins can review the details of each tool, including its input schema, output schema, and annotations. This helps admins understand what data the tool accepts, what response it returns, and any additional metadata associated with the tool. 5. **Review and reauthorize schema changes:** After an admin authorizes a server, any subsequent changes to tool schemas will require admin review and re-authorization. The admin must review the updated schema and re-authorize to update the approved baseline. This applies regardless of whether the tool signature change setting allows continued access - re-authorization is always needed to formally approve the new schema. ![Agentic App Review Page]()
Similar functionalities are available in the Resources and Prompts pages.

AI in Webex

Production create multi-category canary 20260918

anchorOverview

In This Article