An authorised operator can use a management MCP connection to inspect and configure the installation. This is different from a customer connection that calls business tools. Do not give management access to an unrelated customer on a shared installation.
Available management operations#
The verified management catalog includes listing, getting, creating and updating servers; and listing, getting, creating, updating and deleting tools. These nine actions describe the verified catalog, not permission for an AI to execute every change without an authorised task.
Management catalog availability can change. Discover it on the actual installation rather than assuming an old tool count or another connector's cached schema is current.
Begin with inspection#
Ask the AI to list servers and identify the intended stable ID. Retrieve the current server or tool before editing so that existing inputs, mappings and settings are preserved. Never paste secrets into a management prompt or a tool's example headers.
Prepare a bounded change#
Inspect the intended test server and summarise its current state.
Prepare the smallest change for the documented API operation.
Set inbound authentication explicitly and keep unverified tools
inactive. Preserve existing unrelated configuration.A new private server must not rely on a creation default that leaves authentication off. If a management action cannot securely configure a credential, complete that part through the approved connection route rather than embedding the credential in the tool definition.
Verify and retain rollback#
Read the saved state back and run the agreed task through the intended client connection. Keep a secret-safe rollback record. A permanent tool deletion can break connected clients and needs a deliberate decision; deactivation is often a safer way to withdraw an unverified operation.