Environments and Companies

A rule in MCP Guard limits the companies an AI assistant may use for a user or a security group, and names the company the connection opens in. Rules belong to one Microsoft Dynamics 365 Business Central environment and are shared by all its companies. To cover several environments, install the extension and make the rules in each of them.

Before you start

You need the permission set MCP GUARD - ADMIN and an MCP Guard licence. The user or security group needs a line on the MCP Guard User Settings page. See Set Up Rules per User and Security Group.

Limit the companies

Choose the search icon (Tell Me), enter MCP Guard User Settings, and then choose the related link.
On the line of the user or security group, choose the assist button in the Allowed Companies field.
On the Select Companies page, select one or more companies, and then choose OK.
In the Default Company field, choose the company the connection opens in.

You can also type the company names in the Allowed Companies field, separated by semicolons. Business Central checks that every company exists in the environment.

What the fields mean

Allowed Companies holds the companies the AI assistant may use. Leave the field empty to allow every company the user has permissions in. An empty field does not block anything.

Default Company is the company the connection opens in. When the field is empty, or names a company that is not allowed, the first allowed company is used.

The list never gives a user more than Business Central does. The BC MCP Pro connector combines the allowed companies with the companies in which the user has permissions, and only offers companies that are in both. When the two do not overlap, the connection fails with a message that names the companies. See Troubleshoot the BC MCP Pro Connector.

Rules are per environment

The extension and its rules live in the environment. The rules are not stored per company: one rule for a user applies whichever company the MCP client reaches first. This has two consequences.

A sandbox environment and a production environment each have their own rules. A rule you make in the sandbox does not exist in production.
An environment without the extension has no rules.

The connector can work in one environment or in several. With several environments, it reads the rule once per environment where the user has permissions, and keeps the environments where the extension admits the user. See Connect with the BC MCP Pro Connector.

What the company list is, and what it is not

Important

The allowed companies, the default company and the MCP configuration are a policy that the connector applies. They are not a security boundary. A user who connects with another MCP client can still reach every company in which they have Business Central permissions. To keep a user away from a company or from data, use permission sets.