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_status_override_delete_apply
Remove a transition mail per object or package through AI.
tool_config_status_override_delete_plan
Show the intended removal of a transition mail per object or package through AI.
tool_config_status_override_set_apply
Create or change a transition mail per object or package through AI.
tool_config_status_override_set_plan
Show the intended change of a transition mail per object or package through AI.
tool_config_status_set_apply
Change a booking status through AI.
tool_config_status_set_plan
Show the intended change of a booking status through AI.
tool_config_telnyx_diagnose
Retrieve a diagnosis of the Telnyx voice assistant (flow, MCP tools, recent conversations) through AI.
tool_config_template_create_apply
Create a template through AI.
tool_config_template_create_plan
Show the intended creation of a template through AI.
tool_config_template_describe
Retrieve templates and their content through AI.
