Skip to main content

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.

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.

SectionUse it toWhen no rule sets it
Server accessAllow or deny a connection by server, person, Smart Group, agent, route, identity provider, or network.The connection is denied.
Hidden from OneMCPDeny access through OneMCP while letting the other rules decide direct access.There is no additional OneMCP-only restriction.
  1. 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.
  2. Choose the servers and callers under Applies to, and set the outcome.
  3. Check Reads as, then Save to draft.
  4. 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.