General Access
General Access is the access level of an MCP Guard rule for everything an AI assistant can reach in Microsoft Dynamics 365 Business Central outside the MCP Guard extension's own API pages. That is Microsoft's own API pages, such as sales and purchase orders, customers, items and journals, and queries. General Access uses the same four levels as the module levels, on the same rule. The BC MCP Pro connector applies it, not Business Central.
The levels
| Level | The AI assistant may |
|---|---|
| Read | Only read. Every rule starts at this level. |
| Modify | Also change records. |
| Create and Actions | Also create records, delete records and run actions. |
| Posting | Also post. |
Each level includes the ones before it.
Set the level
- 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 level in the General Access field.
You need the permission set MCP GUARD - ADMIN and an MCP Guard licence to change a rule. See Set Up Rules per User and Security Group.
Every rule starts at Read
A new rule starts at Read. The rules that existed before version 1.12.0.0 of the extension also start at Read. With a connector that knows the field, nobody creates, changes or posts through the AI assistant on Business Central's standard pages until an administrator raises the level.
Tip
Raise the level on your own rule first.
The connector enforces it, not Business Central
The extension has no hook on Business Central's standard tables, and it cannot tell a call from an AI assistant from any other API call. So the extension only stores the level and reports it as generalAccess on the mcpUserSettings API page. See Connect with the BC MCP Pro Connector.
The BC MCP Pro connector hides and refuses the actions above the level. It needs version 0.8.0 or later of the connector, or version 0.11.0 or later of the cloud edition. An older connector ignores the field, and the limit then does not apply.
What General Access does and does not do
- It limits the assistant, not the user. In the Business Central client, in Excel or in another application, the user keeps their own permissions. With another MCP client, the same user can still reach the MCP server of Business Central directly. Permission sets remain the hard boundary.
- It never gives more than the user's own Business Central permissions and the MCP configuration of the rule.
- The two scopes are separate. General Access does not cover the extension's own API pages, and the module levels do not cover Microsoft's pages. A planner with General Access on Read and Planning Access on Create and Actions still plans. Posting in General Access does not open a module.