Every tool behind the configuration door /mcpconfig has a right of its own. That right is necessary but never enough.
The chain
tool_config_use— the master switch. Without this right the tool list is empty.tool_config_<tool>— one right per tool. Plan and apply each have their own right, so you can let someone look without letting them change anything.- The functional right behind the tool — the very same right the screen uses.
- When writing: both configuration locks must be open. Tools with level 2 are not run on a production environment.
Who holds these rights?
The rights sit in the MCP-Config group, together with the functional rights the tools need. A fresh install gets that group automatically; on an upgraded environment you set it up with the button on Configuration → AI settings → Tools. Either way the group starts without members: adding someone to the group is the step that turns configuring through AI on for that person.
What the tools do is described on MCP configuration tools.
tool_config_payment_schedule_set_plan
Show the intended change of a payment instalment through AI.
tool_config_pricing_explain
Retrieve an explanation of the price build-up through AI.
tool_config_product_set_active_apply
Activate or deactivate a product through AI.
tool_config_product_set_active_plan
Show the intended activation or deactivation of a product through AI.
tool_config_recent_changes
Retrieve recent configuration changes through AI.
tool_config_resource_create_apply
Create a resource through AI.
tool_config_resource_create_plan
Show the intended creation of a resource through AI.
tool_config_resource_describe
Retrieve resources and their linked objects through AI.
tool_config_resource_update_apply
Change a resource through AI.
tool_config_resource_update_plan
Show the intended change of a resource through AI.
