Choose the plugin tools an agent can use
Open in AgentumPurpose
Kian has connected the inventory plugin, but the support assistant cannot use it until he says so. Give the agent access to your connected plugins, and limit it to the tools you want it to use.
Before you start
The custom agent must belong to your current workspace, you need permission to manage agents, and the plugin must be connected for you first (see "Connect a plugin"). Workspace rules decide which plugins you can connect.
Steps
- Open "Agents", find the agent under "My agents" and select it. In the window, open "Agent actions" (the three dots) and choose "Edit agent".
- Open "Plugins". If it says "No connected plugins", connect one from the Plugins page first. Use "Search plugins or tools" to find a plugin by name, developer, capability or tool.
- Under "Connected plugins", switch on each plugin the agent may use. A plugin you added yourself carries the "Personal" badge. A switched-on plugin shows "All tools enabled" by default.
- To allow only some tools, select "Choose tools" and tick the ones to allow. At least one tool always stays ticked. A saved configuration can hold up to 50 plugins, and up to 200 explicitly chosen tools per plugin ("All tools enabled" is not counted against the 200). "Use all" brings back the full list, and "Hide tools" closes the list.
- Switch a plugin off to give the agent none of its tools.
- Below the list, "Tool middleware" holds retries, the tool call limit and the tool selector (see "Set agent execution limits").
- Select "Save" and test with a request that needs one of the allowed tools.
Expected result
The agent can use only the tools you left ticked, and only while the plugin stays connected for you.
Troubleshooting
| Problem | What to do |
|---|---|
| A plugin does not appear | Only connected plugins are listed. Connect it first, then reopen the editor. |
| A plugin shows no tools | Reconnect it so its tools are discovered again. |
| The agent cannot use a tool you ticked | The plugin was disconnected, or a workspace rule does not allow it. |