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.
- Classic settings
- Policy Engine
Configure it on the server
The section reads: "Rules override the base settings for a smart group or a single user. User rules apply after group rules." The card's Scoped rules chip shows how many rules the server has.
Add a rule
- Click Add rule.
- Under Applies to, select A smart group and choose the Smart group, or select A single user and enter the User email.
- Leave Rule active on. Turning it off stops applying this override; it does not block the server.
- Set only the overrides you need. Anything left at Inherit keeps the server's base setting.
- Click Save rule.
Each saved rule shows a Smart group or User tag, a summary of what it overrides, and Rule active or Rule inactive. Use Edit or Delete to change it.
To decide who may use the server at all, use Server access instead.
What a rule can override
With Justification on, the user must type a reason to approve a confirmed call; denying a call does not require one. Setting Confirmation to On also sets Justification to On. Justification needs Confirmation. See Human approval for how confirmation works.
How rules combine
A person can belong to several smart groups. Their settings are built in three steps:
"Strictest" means, for each field:
A user rule takes precedence, so it can make a group setting less restrictive.
Effective settings preview
Review one user's effective settings after all rules apply.
- Under Effective settings preview, enter a User email.
- Click Resolve.
The preview lists the tools, any hidden tools, token saving and the guardrail actions for that person. Click Show full settings to see everything.
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.
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.
Related
- Server access - allow or deny groups and users on the server.
- Security guardrails - the base guardrail settings rules override.
- Token saving - the base token saving strategies.
- Tool visibility - base tool settings and confirmation.
- Policy Engine overview - how cards, stages and priorities work.