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_template_section_set_apply
Change a template section through AI.
tool_config_template_section_set_plan
Show the intended change of a template section through AI.
tool_config_template_update_apply
Change a template through AI.
tool_config_template_update_plan
Show the intended change of a template through AI.
tool_config_theme_describe
Retrieve theme settings through AI.
tool_config_theme_patch_css_apply
Change part of the extra theme CSS through AI.
tool_config_theme_patch_css_plan
Show the intended partial change of the extra theme CSS through AI.
tool_config_theme_rebuild_apply
Recompile a theme through AI.
tool_config_theme_rebuild_plan
Show the intended recompilation of a theme through AI.
tool_config_theme_set_css_apply
Change the extra theme CSS through AI.
