iam.agent-sessions.revoke-connection

Revoke the connection behind a session: OAuth app disconnected, access key refused by MCP

POST /iam/api/agent-sessions/{id}/revoke-connectionIAM iam:EndAgentSessionChanges stateDestructive

Request syntax

POST /iam/api/agent-sessions/{id}/revoke-connection

Path parameters

  • idRequired

    string

    Constraints: uuid

Response

200 with { connectionId, revoked, kind, accessKeyRowId }: for an access key connection, accessKeyRowId is the key’s id; it still works outside MCP until you deactivate it under access-keys.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow iam:EndAgentSession on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud iam agent-sessions revoke-connection id

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_iam_agent-sessions_revoke-connection.