Firezone

Delete a Client Token

delete_actor_client_token

Delete a Gateway

delete_site_gateway

Delete a Gateway Token

delete_site_gateway_token

Deletes a Group and its memberships. Policies that grant the Group are kept, but their `group_id` becomes null and they grant no access. A Policy for a synced Group is linked again automatically if the Group reappears on a later directory sync. The built-in Everyone Group cannot be deleted.

delete_group

Delete a Policy

delete_policy

Deletes a Site. Deleting is not blocked when the Site still has Gateways or Resources. The Site's Gateways, Gateway tokens, and Resources are deleted with it. Every Policy for those Resources is deleted too, and Clients lose access to them right away. The system-managed Internet Site cannot be deleted.

delete_site

Delete all Client Tokens for service_account, account_user, or account_admin_user actors

delete_all_actor_client_tokens

Delete all Gateway Tokens for a Site

delete_all_site_gateway_tokens

Delete an Actor

delete_actor

Delete an External Identity

delete_actor_external_identity

List Actors

list_actors

List Client Tokens for service_account, account_user, or account_admin_user actors

list_actor_client_tokens

List Clients

list_clients

List Email OTP Auth Providers

list_email_otp_auth_providers

List Entra Auth Providers

list_entra_auth_providers

List Entra Directories

list_entra_directories

List External Identities for an Actor

list_actor_external_identities

List Gateways

list_site_gateways

List GitHub Auth Providers

list_github_auth_providers

List Google Auth Providers

list_google_auth_providers

List Google Directories

list_google_directories

List Groups

list_groups

Retrieves Firezone audit, session, network flow, or REST API request logs for the authenticated account. Use this to investigate configuration changes, review session activity, or troubleshoot network access and API requests. Returns a page of log entries, most recent first. - `change`: audit entries recording each insert, update, or delete event against an account-scoped object, most recent first. - `session`: one entry per Client, Gateway, or Portal session created, most recent first. - `flow`: one entry per network flow reported by Clients and Gateways, most recently started first. - `api_request`: one entry per authenticated REST API request, most recent first. Select one log stream with the required `type` argument. Narrow results with `begin` and `end` RFC 3339 timestamps, for example `2026-05-26T00:00:00Z`. The inclusive window applies to the entry's `timestamp`, or `flow_start` for flows. Non-UTC offsets are converted to UTC. The default window is the last 90 days; `begin` must not be later than `end`. Results can be further narrowed by `actor_id` (every type) or `actor_email` (`change`, `session`, and `flow`), which matches the email recorded when the entry was created. API requests are made by API clients, which have no email, so `actor_email` is not supported for `api_request`. Returns up to `limit` entries (default 50, maximum 100). Pass the `next_page` cursor from the response's `metadata` as `page_cursor` to retrieve the next page.

list_logs

Lists the Actors in a Group. The built-in Everyone Group has no explicit memberships. For it, this lists every user and admin Actor in the account, which is who the Group grants access to. Service accounts and API clients are never members of the Everyone Group.

list_group_memberships

List OIDC Auth Providers

list_oidc_auth_providers

List Okta Auth Providers

list_okta_auth_providers

List Okta Directories

list_okta_directories

List Policies

list_policies

Lists the devices synced from the account's posture providers of one `type`. Some types have close to 100 fields per device, so pass `fields`.

list_posture_devices

Lists every field a Policy's `postures` expression can test, with its type, operators, and platforms. Filter by `provider` to keep the response small. One node of a Policy's device posture expression. A node has exactly one of these shapes: * `and`: a non-empty list of nodes that must all hold. * `or`: a non-empty list of nodes of which at least one must hold. * `not`: a node that must not hold. * a leaf: a `field`, an `op`, and for most operators a `value`. A leaf's `field` is `<provider>.<attribute>`, such as `intune.compliance_state` or `firezone.last_seen_version`. The provider is one of `firezone` (the connecting device's own record), `intune`, `iru`, `defender`, `santa`, `sentinelone` or `sophos`. The attribute is one of that provider's synced device attributes. Every synced provider also has a boolean `enrolled` that is true when the provider knows the device. The attribute's type decides which operators apply and what `value` must be: * strings: `is`, `is_not`, `is_in`, `is_not_in`, `contains`, `does_not_contain`, `starts_with`, `ends_with`, `matches`, `does_not_match`. Comparisons ignore case. `is_in` and `is_not_in` take a list of strings. `matches` and `does_not_match` take a regular expression. * booleans: `is` with `true` or `false`. * numbers: `eq`, `ne`, `gt`, `gte`, `lt`, `lte`. * versions: `is`, `is_not`, `gt`, `gte`, `lt`, `lte`, compared segment by segment, so `14.4` equals `14.4.0`. * timestamps: `before` and `after` with an ISO 8601 datetime such as `2026-01-01T00:00:00Z`; `within_last` and `not_within_last` with an ISO 8601 duration such as `PT24H` or `P30D`. A date-only attribute counts as the start of that day in UTC. * IP addresses: `is_in_cidr` and `is_not_in_cidr` with a list of CIDRs. `firezone.ipv4` takes IPv4 CIDRs only and `firezone.ipv6` IPv6 only. * lists of strings: `contains`, `does_not_contain`, `contains_any_of`, `contains_all_of`, `is_empty`, `is_not_empty`. * JSON attributes: `is_empty`, `is_not_empty`. The value `@latest` on `firezone.last_seen_version` stands for the newest Client release for the device's platform. `enum_string` uses the string operators; `integer` and `float` use the numeric operators. `string_array` values use a single string for `contains` and `does_not_contain`, or a non-empty string list for `contains_any_of` and `contains_all_of`. Every attribute also accepts `exists` and `does_not_exist`. These and `is_empty` / `is_not_empty` take no value: omit `value` or set it to null. Missing attributes fail every operator except `does_not_exist`, including negative operators such as `is_not`. A missing provider is evaluated as one empty row. Its synthetic `enrolled` field is false, so `enrolled is false` can explicitly match an unenrolled device. `not` negates the result and can also match missing data; use a positive `enrolled is true` check when enrollment is required. Leaves that do not apply to the device's platform are removed before evaluation, including inside `or` and `not`. An expression with no applicable leaves passes. If the platform is unknown, no leaves are removed. Each field lists the platforms it applies to. Provider `os_up_to_date` fields are computed from known OS releases; they are not raw provider attributes. When a device matches more than one record of a provider, a leaf holds when any record satisfies it. Set `rows` to `all` to require every record. Different leaves may match different provider rows; `and` does not require one row to satisfy all leaves. `rows` is not allowed for `firezone`, which always describes exactly one connecting device. Expressions allow at most 10 nested boolean levels and 100 leaves. List values contain 1–100 items; strings are at most 1024 bytes and regular expressions at most 256 bytes. Unknown fields, incompatible operators, invalid values, and exceeded limits return HTTP 422 with a path in `validation_errors.postures`.

list_posture_fields

Lists the account's posture providers of one `type`. A posture provider syncs device data from an MDM or EDR product so Policy `postures` can test it.

list_posture_providers

List Resources

list_resources

List Sites

list_sites

Creates a Gateway and mints its single-owner token in one call. The token is returned once here - store it securely. If it's lost, rotate it via `POST /sites/{site_id}/gateways/{gateway_id}/token/rotate` once the Gateway has connected, or delete and re-provision it. `name` is optional; a random name is generated when omitted. `ipv4` and `ipv6` are the Gateway's tunnel addresses, allocated from the account's pool when the Gateway row is created - they are always present in this response, before the Gateway has ever connected. Request body for provisioning a Gateway

create_site_gateway

Mints a replacement token for the gateway. A current token the gateway has connected with keeps working until the gateway first connects with the replacement or 4 hours elapse, whichever comes first; a token no gateway has ever connected with is replaced immediately. Rotating again before the gateway picks up the replacement replaces only the pending token and never invalidates the one in use. Once the replacement is confirmed the previous token is deleted - rolling the gateway's configuration back to it will strand the gateway. Security-sensitive: returns a live credential to the MCP client. Disconnecting OAuth does not revoke credentials issued by this tool.

rotate_single_owner_gateway_token

Show Account

get_account

Show Actor

get_actor

Show Client

get_client

Show Email OTP Auth Provider

get_email_otp_auth_provider

Show Entra Auth Provider

get_entra_auth_provider