Topolo Docs Topolo Platform
Open workspace

Revoke Insights collection key

Permanently revoke one selected workspace collector.

Outcome

Permanently revoke one selected workspace collector.

Before you start

  • Verify the exact identity, environment and approved organization with topolo whoami before discovering this action.
  • Inspect the credential-scoped action and canonical resource discovery. Examples use synthetic resources; replace their handles only with separately verified targets.
  • Validate the complete input and review the action plan. Mutation and organization-inventory actions require explicit confirmation; a successful shape check does not prove a runtime grant.
  • Select a granted workspace through topolo resources. The CLI/MCP supplies canonical resource headers; workspace identity is not an arbitrary payload field.

Discover the target

topolo whoami --json
topolo apps get topolo-insights --json
topolo actions get app_topolo_insights.collection_sites.revoke --detail --json
topolo resources topolo-insights --json

Request

DELETE /api/collection-sites/{siteId} · permission workspace:write · confirmation required.

Inspect schemas and test this action in the signed action console. The complete field schema is also available through CLI/MCP action discovery.

Effects and scope

  • Requires workspace admin access and an existing active collector id. Returns HTTP 204 with no response body.
  • Future use of that key is refused. Historical analytics and archives remain. Repeating the revoke returns not_found; it is not a second successful mutation.

Interpret the response

  • Interpret HTTP 204 as success without expecting an id or JSON object.
  • Re-read collection_sites.list and inspect that exact collector status. Historical data is not evidence that revocation failed.

Worked requests and responses

Actual exported Insights worker, all nine migrated D1 scripts and isolated local R2. Auth identity/grants/archive transport, queue delivery and Analytics Engine sink are synthetic; local queue processing is called explicitly. Notify and Nexus are disabled. No live website, provider, paid usage or deployed data erasure is tested. Successful and refused captures below are separate examples. A refused response is a boundary, not a successful task.

workflow · refusal 1 · HTTP 404

Actual exported Insights worker, all nine migrated D1 scripts and isolated local R2. Auth identity/grants/archive transport, queue delivery and Analytics Engine sink are synthetic; local queue processing is called explicitly. Notify and Nexus are disabled. No live website, provider, paid usage or deployed data erasure is tested. Selected synthetic workspace: ws_insights_workflow. Fixture handles authorize no live request.

Input · payload.json:

{
  "siteId": "site_missing"
}

CLI:

topolo actions validate app_topolo_insights.collection_sites.revoke --data @payload.json --json
topolo actions plan app_topolo_insights.collection_sites.revoke --data @payload.json --confirm --json

Captured raw Worker result

{
  "error": "not_found"
}

HTTP 404. Re-discover the exact resource id in this workspace. A missing or revoked/deleted record cannot be repaired by inventing a new id.

CLI/MCP adds its transport envelope; CLI --detail retains the full action result.

workflow · success 2 · HTTP 204

Actual exported Insights worker, all nine migrated D1 scripts and isolated local R2. Auth identity/grants/archive transport, queue delivery and Analytics Engine sink are synthetic; local queue processing is called explicitly. Notify and Nexus are disabled. No live website, provider, paid usage or deployed data erasure is tested. Selected synthetic workspace: ws_insights_workflow. Fixture handles authorize no live request.

Input · payload.json:

{
  "siteId": "63038c5f-1b3f-4bb2-b885-231e6362a465"
}

CLI:

topolo actions validate app_topolo_insights.collection_sites.revoke --data @payload.json --json
topolo actions plan app_topolo_insights.collection_sites.revoke --data @payload.json --confirm --json
topolo actions call app_topolo_insights.collection_sites.revoke --data @payload.json --confirm --detail --json

MCP tool and arguments:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_insights.collection_sites.revoke",
    "input": {
      "siteId": "63038c5f-1b3f-4bb2-b885-231e6362a465"
    },
    "confirm": true
  }
}

Captured raw Worker result

(empty response body)

SDK/CLI/MCP action result:

""

HTTP 204. Interpret HTTP 204 as success without expecting an id or JSON object. Re-read collection_sites.list and inspect that exact collector status. Historical data is not evidence that revocation failed. The raw HTTP response has no body. The Topolo SDK, CLI and MCP represent this result as an empty string, not JSON null.

CLI/MCP adds its transport envelope; CLI --detail retains the full action result.

workflow · refusal 3 · HTTP 404

Actual exported Insights worker, all nine migrated D1 scripts and isolated local R2. Auth identity/grants/archive transport, queue delivery and Analytics Engine sink are synthetic; local queue processing is called explicitly. Notify and Nexus are disabled. No live website, provider, paid usage or deployed data erasure is tested. Selected synthetic workspace: ws_insights_workflow. Fixture handles authorize no live request.

Input · payload.json:

{
  "siteId": "63038c5f-1b3f-4bb2-b885-231e6362a465"
}

CLI:

topolo actions validate app_topolo_insights.collection_sites.revoke --data @payload.json --json
topolo actions plan app_topolo_insights.collection_sites.revoke --data @payload.json --confirm --json

Captured raw Worker result

{
  "error": "not_found"
}

HTTP 404. Re-discover the exact resource id in this workspace. A missing or revoked/deleted record cannot be repaired by inventing a new id.

CLI/MCP adds its transport envelope; CLI --detail retains the full action result.

permission-refusals · refusal 4 · HTTP 403

Actual exported Insights worker, all nine migrated D1 scripts and isolated local R2. Auth identity/grants/archive transport, queue delivery and Analytics Engine sink are synthetic; local queue processing is called explicitly. Notify and Nexus are disabled. No live website, provider, paid usage or deployed data erasure is tested. Selected synthetic workspace: ws_insights_merge. Fixture handles authorize no live request.

Input · payload.json:

{
  "siteId": "site_example"
}

CLI:

topolo actions validate app_topolo_insights.collection_sites.revoke --data @payload.json --json
topolo actions plan app_topolo_insights.collection_sites.revoke --data @payload.json --confirm --json

Captured raw Worker result

{
  "success": false,
  "error": {
    "code": "action_permission_required",
    "message": "Action \"collection_sites.revoke\" requires permission \"workspace:write\".",
    "action": "collection_sites.revoke"
  }
}

HTTP 403. The credential lacks the declared action permission. Inspect credential-scoped discovery in the same approved context; workspace role does not replace the permission.

CLI/MCP adds its transport envelope; CLI --detail retains the full action result.

Verify the outcome

  • Interpret HTTP 204 as success without expecting an id or JSON object.
  • Re-read collection_sites.list and inspect that exact collector status. Historical data is not evidence that revocation failed.

Errors and recovery

  • not_found (HTTP 404): Re-discover the exact resource id in this workspace. A missing or revoked/deleted record cannot be repaired by inventing a new id.
  • action_permission_required (HTTP 403): The credential lacks the declared action permission. Inspect credential-scoped discovery in the same approved context; workspace role does not replace the permission.

Only observed refusals are listed. This does not promise that external dependencies or every invalid payload have been exhaustively exercised.

Recovery boundary

A revoked secret cannot be reactivated by a published action. Create a replacement only after reviewing origins and mode; update the intended website with its new key. Previous events are retained.

Evidence and limits

Actual exported Insights worker, all nine migrated D1 scripts and isolated local R2. Auth identity/grants/archive transport, queue delivery and Analytics Engine sink are synthetic; local queue processing is called explicitly. Notify and Nexus are disabled. No live website, provider, paid usage or deployed data erasure is tested.