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_menu_set_items_apply
Change menu items through AI.
tool_config_menu_set_items_plan
Show the intended change of menu items through AI.
tool_config_object_copy_apply
Copy an object into a new object through AI.
tool_config_object_copy_plan
Show the intended copy of an object through AI.
tool_config_object_create_apply
Create an object through AI.
tool_config_object_create_plan
Show the intended creation of an object through AI.
tool_config_object_explain
Retrieve an explanation of the object settings through AI.
tool_config_object_set_attributes_apply
Set object attributes (address, GPS, custom fields) through AI.
tool_config_object_set_attributes_plan
Show the intended change of object attributes (address, GPS, custom fields) through AI.
tool_config_object_set_calendar_apply
Set the calendar of an object through AI.
