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_homepage_set_plan
Show the intended change of the homepage through AI.
tool_config_language_activate_apply
Switch a language on or off through AI.
tool_config_language_activate_plan
Show the intended switching on or off of a language through AI.
tool_config_language_list
Retrieve languages and translatable parts through AI.
tool_config_language_missing_report
Retrieve missing translations per language through AI.
tool_config_media_fetch_apply
Fetch a file from a URL into the media library through AI.
tool_config_media_fetch_plan
Show the intended fetch of a file into the media library through AI.
tool_config_media_upload_link_apply
Create a one-time upload link for the media library through AI.
tool_config_media_upload_link_plan
Show the intended upload link for the media library through AI.
tool_config_menu_describe_items
Retrieve menu items through AI.
