Hanzo
Cloud MCPcloud

adminApplications

Lists IAM applications for one owner org, forwarded VERBATIM from IAM's get-applications.

Lists IAM applications for one owner org, forwarded VERBATIM from IAM's get-applications. These are the platform's OIDC clients — the console reads clientId off each row.

TooladminApplications
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments3
OperationGET /v1/admin/applications
Productcloud

Arguments

FieldTypeRequiredDefaultDescription
ownerstringOwner is the org whose rows to read. Defaults to the admin org, which owns the platform's roles and applications.
pstringPage is the 1-based page number. Forwarded only when set — IAM applies its own default otherwise.
pageSizestringPageSize is rows per page. Forwarded only when set.

This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "adminApplications",
         "arguments": {
           "owner": "<owner>",
           "p": "<p>",
           "pageSize": "<pageSize>"
         }
       }
     }'

Values are placeholders derived from each field's declared type. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →

The operation behind it

OperationRouteProductSummary
cloud_adminApplicationsGET /v1/admin/applicationscloudLists IAM applications for one owner org, forwarded VERBATIM from IAM's get-applications.

The same capability over plain HTTP is in the cloud API reference, on https://api.hanzo.ai.


All 834 tools · The door · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).

How is this guide?

On this page