Control Which Tools Users Get
Decide which tools each user can reach on the Dynamic Gateway, and deliver them only through the toolkits you assign.
Three controls shape the tools a person gets on their Dynamic Gateway. Each one answers a different question, and they apply in a fixed order.
| Control | Where | Question it answers |
|---|---|---|
| App Tools | App Management → the app → Tools | Which of this app's tools can anyone use at all, and which can each user or group use? |
| Admin toolkits | Dynamic Admin Controls | Which tools does an admin hand to a user, a group, or the whole organization? |
| Personal selections | The user's own hub | Which of their allowed tools does the user turn on for themselves? |
App Tools is the limit. A toolkit or a personal selection delivers tools from inside that limit. A tool that isn't allowed in App Tools for a user stays unavailable to them, whichever toolkit it appears in.
Auxiliary (static) Gateways are separate endpoints with their own tool selections. They don't change what a user's Dynamic Gateway serves.
Before you start
| Task | Permission |
|---|---|
| Set an app's tools in App Management | MCP → App Settings → Read and MCP → App Management → Manage |
| Build and assign admin toolkits | MCP → Gateway/Toolkit Assignment → Manage |
| Create a custom role | Permission to manage roles. See Custom Roles. |
See the permissions reference for what each permission covers.
Set the limit for an app
Go to Secure → Gateway → App Management and open the app.
Select Tools. The App Tools panel opens with Configure tools for set to All users.
Select the tools everyone in your organization may use, then click Save App Tools.
To allow a different set for specific people, change Configure tools for to those users or groups, select their tools, and click Save App Tools.
Deliver tools only through assigned toolkits
Use this setup when people should get exactly the tools you assign, with no toolkits of their own.
Create a custom role that includes MCP → Dynamic Gateway → Use and leaves out MCP → Dynamic Gateway → Manage. Use lets a person connect to the Dynamic Gateway, connect their own accounts, and receive the toolkits you assign. Manage adds creating personal toolkits.
Every built-in role, including End User, includes Dynamic Gateway → Manage, and a person's roles add together. Assign the custom role to these users in place of a built-in role, so Use is the only Dynamic Gateway permission they hold.
In the MCP section of the navigation, open Dynamic Admin Controls and create an admin toolkit. Add the apps, then select the tools the toolkit delivers.
Set Assignment mode to Locked when the toolkit must stay on for everyone who receives it. See Locked and Editable toolkits.
Assign the toolkit to the groups that need it. Group assignments follow membership, so new team members receive the toolkit automatically.
Keep App Tools as the outer limit for each app. The toolkit decides which of those tools each group receives.
Locked and Editable toolkits
| Editable | Locked | |
|---|---|---|
| Recipient can hide the whole toolkit | Yes | No |
| Recipient can switch off a single tool inside it | No | No |
| A personal mute on one of its apps | Removes that app for the user | The toolkit keeps its apps on |
| Changing tools in the toolkit | Admins only | Admins only |
Switching a toolkit from Editable to Locked turns it back on for anyone who had hidden it.
How users see their tools
Users manage connections in the App Catalog in their hub. The catalog lists apps from their toolkits that still need a connection first, so people can sign in before their first task. Muting an app there takes it out of that user's gateway for a while without disconnecting it or changing any toolkit. Apps delivered by a Locked toolkit stay on even when muted, with the tools that toolkit selects.
An assigned toolkit controls which tools a person receives, not their sign-in. Apps that act as the user, such as Jira or Microsoft Graph, still need each person to connect their own account once. Apps configured with a shared organization credential work right away. See Tenant vs. Personal App Credentials.
How the AI client sees your setup
Toolkits organize tools for people in Airia. The AI client sees one Dynamic Gateway and the individual tools it serves, and finds them through Radar. Toolkit names and descriptions stay in Airia.
To steer how a model uses an app's tools, write app instructions or publish a skill through Skills over MCP.
Confirm the result
Changes to App Tools and toolkits apply to the gateway as soon as you save them.
- Ask a user in the group to start a new chat in their AI client.
- Have them ask the client to call a tool you left out of their toolkit.
- The gateway answers that the tool is not permitted, and the call appears as Denied in MCP Monitoring.
Tools outside a user's allowed set don't appear in their Radar search results.