Server access
Updated on 3 November 2026.
Choose which AI agents, Smart Groups and people can connect to an MCP server. Connection access is separate from permission to list or call its tools.
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
Scroll to the Access control card.
Adding a group or person to one side removes it from the opposite list. Click Save settings in the footer to apply your changes.
To manage agents across every server at once, use the Allowed Agents button in the MCP Gateway header. It edits the same agent list. See Allowed Agents.
Precedence
The card reads: "Denied users take precedence. An explicitly allowed user can override a denied smart group; user rules are matched case-insensitively."
The gateway checks each person in this order and stops at the first match:
Emails match regardless of case, so Jane@Example.com and jane@example.com match the same email address.
Allowed agents is checked separately. A request from a client whose User-Agent matches no allowed agent is denied regardless of the user.
The User-Agent identifies a client but does not authenticate it, so treat Allowed agents as steering, and rely on the user and group lists for access decisions. See Allowed Agents.
These rules apply to calls that go through the MCP Gateway. They do not stop someone from connecting to an MCP server directly from their own client. To find and close those paths, see An MCP server outside the gateway.
Example
- A contractor is denied access.
lead@example.comis allowed even though they are inContractors.former.admin@example.comis denied access even if they are in an allowed group.
How it relates to other settings
Going further with the Policy Engine
Open Govern > Policy Engine > MCP Gateway > Controls > MCP Server Access. The panel shows what happens today, recipes, configured rules, and an Activity tab.
- Choose a recipe such as Let a team connect to a server or Keep someone off a server, or start a blank rule in the section.
- Choose the servers and callers under Applies to, and set the outcome.
- Check Reads as, then Save to draft.
- Use Test > Try a situation to check an allowed and a denied caller, then review and publish.
For both sections, the highest numeric priority wins; Deny wins only when priorities tie. A higher-priority Allow can therefore override a lower-priority Deny. Scope suggests a starting priority; it does not replace the stored priority of an existing rule.
Allowing a connection does not allow its tools. Configure Invocation & Discovery for what is listed, what can run, and which results return. See Tool visibility.
OneMCP Features, in the same Who can connect? group, controls dynamic tools, memory, and short tool lists.
Related
- Allowed Agents - register custom agents and set servers per agent.
- Group and user rules - override settings for a smart group or a single user.
- Claims forwarding - pass the signed-in user's identity to the server.
- Policy Engine overview - how cards, stages and priorities work.