Articles in this section

Assign a network policy

Kathyana Queeman
Updated

Assign a network policy to control where an MCP server, an API token, workspace-user sign-in, or end-user authentication can be reached from. Each server, token, and restriction holds one policy, and you can assign the same policy to as many of them as you like. An assignment takes effect within about 30 seconds, and until you assign a policy, a server or token accepts requests from any address.

For how Celigo evaluates a policy and what a blocked caller sees, see Network policies overview. To create a policy first, see Create and manage network policies, or create one from any Network policy field as you go.

Prerequisites:

  • You're signed in as an account owner or administrator.
  • You're working in the environment that holds the server, token, or users you want to restrict. A policy can only be assigned within the environment where it was created.
  • The policy includes the public addresses your callers or users connect from. For a sign-in restriction, that includes your own.

Assign a policy to an MCP server

A server policy applies to every call to the server, whichever authentication method the caller uses.

  1. Go to AI studio > MCP servers, and then select the MCP server.
  2. Select the Access tab, and then select Governance.
  3. In Network policy, select a policy. To create one, open the list and select Create network policy.
  4. Select Save.

Within about 30 seconds, the server refuses calls from addresses the policy doesn't allow with Access denied., before any tool runs. Each blocked call appears in the server's request logs as an errored call with status 403. Calls from allowed addresses are unchanged.

Note: The end-user restriction under Account > Security applies to end users who sign in with OAuth, not to API tokens or personal access tokens (PATs). To restrict token traffic to this server, assign a server policy, or assign a policy to the token itself.

Assign a policy to an API token

A token policy applies to every call that authenticates with the token, to any endpoint, in addition to any policy on the endpoint itself.

  1. Go to Resources > API tokens.
  2. Select Actions (…) next to the token, and then select Edit token. To restrict a new token, select Generate token instead. The Create service token drawer opens.
  3. In General, in Network policy, select a policy.
  4. Select Save.

Calls with the token from addresses the policy doesn't allow receive HTTP 403 with Access denied. on every endpoint, including MCP servers. When you open the token, its Network policy section shows the assigned policy with a View policy button that opens the policy read-only. Token blocks are recorded in Celigo's internal logs only — if a caller reports Access denied., compare their public address with the policy.

Personal access tokens have no Network policy field. A PAT follows the workspace-user sign-in restriction of the environment it was created in. See Restrict workspace-user sign-in to approved IP addresses.

Restrict workspace-user sign-in to approved IP addresses

This restriction applies to every workspace user of the environment at sign-in and at each account or environment switch. It also applies to every PAT created in the environment, on every call. It doesn't end sessions that are already open, and the Celigo support user is exempt. API tokens, which have their own Network policy field, and SCIM provisioning tokens aren't checked against it. It's separate from the end-user restriction, which has its own checkbox and its own policy.

  1. Go to Account (the avatar at the top of the page), select Security, and then select Governance from the left menu.
  2. Select the IP-based access restriction checkbox. The Network policy field appears below it — it holds one policy and is required while the restriction is on.
  3. In Network policy, select the policy that allows your users' networks.
  4. If the warning Your current IP address (203.0.113.5) is not allowed by this policy. Saving may lock you out. appears, edit the policy to include that address, or connect from an approved network before you continue. The warning doesn't prevent the save.
  5. Select Save.

From the next sign-in or switch, a user who connects from an address the policy doesn't allow is signed in but shut out of this environment: an access denied message appears and no account data loads. The user can move to another account or environment they belong to, or sign out. Each denied sign-in or switch is written to the account's audit log with the IP address that was checked and the reason IP address not permitted by network policy. PATs created in the environment receive HTTP 403 with Access denied. from the same addresses. ⚠ VERIFY: the exact wording of the blocked user's in-browser message — check on staging.

To turn the restriction off, clear IP-based access restriction and select Save, or select the trash icon next to the assigned policy. The trash icon removes the assignment immediately.

Restrict end-user sign-in to approved IP addresses

This restriction applies to every end user who signs in to an MCP server in the environment from an AI client, and to every later use of their OAuth token, whichever identity provider they sign in through.

  1. Go to Account (the avatar at the top of the page), select Security, and then under End users, select Authentication from the left menu.
  2. Under Trusted devices, select the IP-based access restriction checkbox. The Network policy field appears below it — it holds one policy and is required while the restriction is on. This checkbox is separate from the workspace sign-in one under Governance, and the two can hold different policies.
  3. In Network policy, select the policy that allows your end users' networks.
  4. Select Save.

Within about 30 seconds, an end user who signs in from an address the policy doesn't allow receives HTTP 403 with Access denied. before Celigo issues a token, and an end user whose token is used from such an address receives the same response on every call. These blocks are recorded in Celigo's internal logs only. An end user who calls a server that has its own policy must pass both.

The Save button here also saves the end-user MFA settings on the same page. The trash icon next to the assigned policy removes the assignment immediately.

Remove a network policy assignment

Every Network policy field shows the assigned policy with an Edit button and a trash icon. The trash icon next to the assigned policy unassigns it from this server, token, or restriction only — the policy stays in the Network policies table, and its other assignments are unchanged. On an MCP server or an API token, select Save afterward. Under IP-based access restriction, the removal is saved at once and the restriction turns off.

The trash icon on a policy's row inside the open Network policy list is different: it deletes the policy for the whole environment, after a confirmation, and the deletion is refused while the policy is assigned anywhere. See Create and manage network policies.

Related articles