dome_status_get, dome_config_get, and dome_platform_keys_available_permissions are visible to any role; the API key tools require apikey.manage at the active scope; and the tenant tools (dome_tenants_list, dome_tenants_get, dome_tenants_create) require the org-level tenant.manage permission.
Status Get
dome_status_get
Get platform status and statistics for the current workspace.
Permission: Authenticated only — visible to any caller with an active context, regardless of role.
Returns workspace statistics including agent counts by status, active rule bundle info, and gateway backend count.
Example tool call
Platform API Keys
Platform API keys authenticate service-to-service integrations with the Dome Platform API.Platform Keys List
dome_platform_keys_list
List platform API keys.
Permission:
apikey.manage
Returns key metadata (name, created date, last used, status) but not the key secret.
Platform Keys Available Permissions
dome_platform_keys_available_permissions
List the permissions you can grant to a new platform API key at the current context’s scope. Read-only. Call this before dome_platform_keys_create to discover the valid permissions values for your role.
Permission: Authenticated only — the server filters the returned set against the caller’s effective role.
Returns an array of
{ id, label } entries. The id is the value to pass to dome_platform_keys_create; the label is a human-readable name for display. The set is scope-aware: a workspace context returns workspace permissions only, a tenant context adds tenant permissions, and an org context adds org permissions.
Example tool call
Platform Keys Create
dome_platform_keys_create
Create a new platform API key for programmatic access. The key is scoped to the current context level (workspace, tenant, or org). The secret is returned once. Call dome_platform_keys_available_permissions first to discover valid permission strings for your role.
Permission:
apikey.manage
Example tool call
Store the returned key secret securely. It cannot be retrieved after creation — only revoked.
Platform Keys Revoke
dome_platform_keys_revoke
Revoke a platform API key permanently.
Permission:
apikey.manage
Config Get
dome_config_get
Get a configuration value from the platform.
Permission: Authenticated only — visible to any caller with an active context, regardless of role.
Tenants
Tools for listing, inspecting, and creating tenants in your active organization. The org is sourced from the active context — switch contexts first if you need to target a different org. All three tools return “No active org context” if the caller has not selected an org context; rundome_context_use to switch.
Tenants List
dome_tenants_list
List tenants under your active organization.
Permission: Org-level
tenant.manage (held by org owner or admin).
Returns the array of tenants visible to the caller, including id, name, plan, org id, default gateway, and creation timestamp.
Example tool call
Tenants Get
dome_tenants_get
Get a single tenant by id from your active organization. The caller is admitted if either the active context is scoped to the requested tenant, or the caller holds org admin or owner on the active org.
Permission: Tenant-scoped session for the requested tenant or org-level
tenant.manage on the active org. The MCP tool listing surfaces this tool when org tenant.manage is held; tenant-scoped callers can still invoke the underlying RPC directly via the API.
Example tool call
Tenants Create
dome_tenants_create
Create a new tenant under your active organization. The caller becomes the initial tenant admin.
Permission: Org-level
tenant.manage (held by org owner or admin).
Creating a new organization is operator-only. Contact Dome to provision a new org.
Example tool call
No active org context. Use dome_context_use first.