edgeapiCachePermissionsInfo

Seen 12 time(s) in 1 run(s).

What it sent and what came back (the newest 3 from our runs)

Read from each run's own recording (rule 73), secrets and signed link tokens taken out. Kept in ~/.logCli/rea/clientFacts.json, so it stays after the run is pruned.

runs/inspect/20261103T065639_mattSlack, step 4: goto /client: 200, 282 ms

Sent:

{
  "query": {
    "_x_app_name": "client",
    "fp": "6f",
    "_x_num_retries": "0"
  },
  "body": "{\"token\":\"xoxc-12165421006739-12156263517591-12492529441700-5bffe6e6a317b9bbab53d938a4526d20e882de6ab372cd46f9f90868bb0322a0\",\"user_id\":\"U0C4L7RF7HD\",\"permissions\":[\"ACCESS_SLACK_AI_TODAY\"],\"as_admin\":true}"
}

Answered:

{
  "allowed": [],
  "allowed_per_team": {},
  "ok": true
}

runs/inspect/20261103T065639_mattSlack, step 6: goto /client/T0C4VCD06MR/D0C8VAE7REU: 200, 184 ms

Sent:

{
  "query": {
    "_x_app_name": "client",
    "fp": "6f",
    "_x_num_retries": "0"
  },
  "body": "{\"token\":\"xoxc-12165421006739-12156263517591-12492529441700-5bffe6e6a317b9bbab53d938a4526d20e882de6ab372cd46f9f90868bb0322a0\",\"user_id\":\"U0C4L7RF7HD\",\"permissions\":[\"ACCESS_SLACK_AI_TODAY\"],\"as_admin\":true}"
}

Answered:

{
  "allowed": [],
  "allowed_per_team": {},
  "ok": true
}

runs/inspect/20261103T065639_mattSlack, step 9: press Control+a: 200, 101 ms

Sent:

{
  "query": {
    "_x_app_name": "client",
    "fp": "6f",
    "_x_num_retries": "0"
  },
  "body": "{\"token\":\"xoxc-12165421006739-12156263517591-12492529441700-5bffe6e6a317b9bbab53d938a4526d20e882de6ab372cd46f9f90868bb0322a0\",\"user_id\":\"U0C4L7RF7HD\",\"permissions\":[\"MANAGE_SALESFORCE_CONNECTIONS\",\"MANAGE_SALESFORCE_MCP_SERVERS\"],\"as_admin\":true}"
}

Answered:

{
  "allowed": [],
  "allowed_per_team": {},
  "ok": true
}

What it does

Asks Slack's cache service which things the account is allowed to look up (allowed, allowed_per_team): it answered allowed: [] and allowed_per_team: {} with ok: true. Seen 5 times in step 4 (goto /client, 73-425 ms), 6 times in step 6 and once in step 9 (press Control+a, 101 ms), all 200.

What our machine does with it

Nothing: no log-cli code calls it. The engine (python/slackApi/engine.py) works through GabrielCore on curl_cffi, which signs in with the d cookie and calls only the web API methods it needs, so this is Slack's own web client boot traffic that log inspect recorded. Gabriel's EdgeAPI calls are users/info and channels/info through call_edge_api (vendor/gabrielSlack/gabriel/client/hydrator.py), neither used by the engine.

What can go wrong

The answer is empty for this account, so the client has no extra permissions to read. If the cache service refuses, the answer carries ok: false and an error; every recorded answer was 200.