rootset_revoke_personal_key - Rootset

Workflow

Access and behavior

Use a personal OAuth connection for the signed-in account. The connection needs keys:manage scope.

This tool changes data or starts work. Confirm the target and input before calling it.
Keep the same idempotencyKey when retrying an unchanged request; use a new key for different input.

Arguments

Argument	Required	Type	Details
`id`	Yes	string	—
`idempotencyKey`	Yes	string	Stable caller-provided key across retries of this exact operation.

Complete input schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "pattern": "^[0-7][0-9A-HJKMNP-TV-Z]{25}$"
    },
    "idempotencyKey": {
      "type": "string",
      "minLength": 8,
      "maxLength": 255,
      "description": "Stable caller-provided key across retries of this exact operation."
    }
  },
  "required": ["id", "idempotencyKey"],
  "additionalProperties": false
}

Example call

Your client initializes the MCP connection before this call. Example identifiers and values are illustrative; use the IDs, schema version and values from your installation.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "rootset_revoke_personal_key",
    "arguments": {
      "id": "01K6J7B8000000000000000000",
      "idempotencyKey": "example-request-0001"
    }
  }
}

Result

Read the structured result returned by the tool. A tool failure sets isError; do not treat an error as a completed operation. The REST operation documents the corresponding result fields and errors. Connect an MCP client · REST conventions