Overview
What Agent Tools are in Uniportal and how they get configured.
What an Agent Tool is
An Agent Tool is a specific action the AI can take on a technician's behalf: create a ticket, look up an asset, reset a password, pull a customer's license count. Where a Skill gives the AI judgment, the procedure and guardrails to follow, an Agent Tool gives it the ability to actually do something in a connected system. A Skill decides what should happen. An Agent Tool carries it out.
Where they come from
You don't add Agent Tools one by one. Connect an Integration, HaloPSA, NinjaOne, IT Glue, and the tools tied to that integration show up on the Agent Tools page automatically. Disconnect the integration and its tools go with it.
Finding a tool
The Agent Tools page lists everything available on your tenant. Search by name, or filter by Integration or by Mode. On a tenant with a few integrations connected, that list gets long fast.
Don't see a tool you need?
Email support@uniportal.ai with what you're trying to do. We ship new tools most weeks, and requests from real workflows are what shape which ones we build next.
Modes: how much rein a tool gets
Every tool has a Mode: Automated, Approval Required, or Disabled, set per tool from the Agent Tools page. See Tool modes for what each one does and how to pick.
Who can use a tool
Access to a tool is role-based, and it's a separate permission set from what a role can do inside Uniportal itself. A custom role might have full management access to Integrations but only a handful of Agent Tools, or the reverse. Admins and Owners can use every tool on the tenant. A custom role only gets the specific tools you grant it, not the full list by default.
That's what lets you get specific: grant a role the Pax8 tools that look up a customer's subscriptions without granting the one that deletes a subscription, without touching anything else the role can do.
That includes new tools. When one shows up, whether it's a new Uniportal tool or one that came in through an integration you just connected, Admins and Owners get it automatically. Your custom roles don't. If a technician on a custom role needs it, you add it to their role yourself.
Disabling a tool overrides all of that. A disabled tool can't be used by anyone on the tenant, Admin included, no matter what their role grants. Role access decides who's allowed to use a tool. Mode decides how the tool behaves and whether it can be used at all.
Referencing tools in a Skill
Type @ in a Skill's instructions and select a tool to reference it directly. That hands the tool straight to the AI instead of leaving it to search the full list for what it needs, though it can still search if the ticket calls for a tool you didn't reference.
Exporting the tool list
Export the full list from the Agent Tools page. It's a plain rundown of every tool available on your tenant, useful if you're handing it to an LLM and asking it to draft a Skill for you: with the real tool names and Integration mappings in front of it, it can write @ references straight into the Skill instead of guessing at what tools exist.