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_page_delete_apply
Delete a page through AI.
tool_config_page_delete_plan
Show the intended deletion of a page through AI.
tool_config_page_describe
Retrieve the page configuration through AI.
tool_config_page_list
Retrieve the page list with usage and source warnings through AI.
tool_config_page_update_apply
Change a content page through AI.
tool_config_page_update_plan
Show the intended change of a content page through AI.
tool_config_payment_schedule_delete_apply
Remove a payment instalment through AI.
tool_config_payment_schedule_delete_plan
Show the intended removal of a payment instalment through AI.
tool_config_payment_schedule_describe
Retrieve payment schedules with instalments, texts and links through AI.
tool_config_payment_schedule_set_apply
Create or change a payment instalment, or link it to an object/package, through AI.
