Skip to main content

Group and user rules

Updated on 3 November 2026.

Give a smart group or a single person different settings on one MCP server. A rule can turn tools on or off, require confirmation, change guardrail actions and enable or disable token saving without changing other users' settings.

Choose the instructions for the mode that governs your MCP Gateway. See Switching from classic settings for what happens to stored settings when the engine is on.

Going further with the Policy Engine​

Caller scope belongs on the control that owns the outcome. Open Govern > Policy Engine > MCP Gateway > Controls, choose the control, then choose people or Smart Groups under Applies to. Use exclusions when a rule should apply to everyone except a group or person.

Classic overridePolicy control
Tool EnabledInvocation & Discovery: listing, calls, and returned results.
Confirmation, JustificationHuman Confirmation.
Guardrail actions and categoriesData & Adversarial Risks.
Token-saving strategiesToken Savings.

Unlike classic overrides, there is no universal “user rule applies last” order. Each control explains How rules combine and When no rule sets this. Access decisions use the highest numeric priority, with Deny winning ties; confirmation and token-saving switches have their own tie rules. Data-risk actions have separate rules for detection actions and the scan profile.

For example, use Invocation & Discovery > Block destructive tools, scope it to a Smart Group, and check which listing, call, and result steps it changes. A more specific audience alone does not guarantee an override: compare its stored priority with the other matching rules.

Policies provides a searchable list of policies and their outcomes. For an effective decision, use Test > Try a situation, choose a person and server/tool, and inspect the result. Replay activity checks the candidate against recorded calls. Review and publish only after the intended and exempt cases behave as expected.