Skip to main content

Control who can use agents

Restrict who can use an agent and where, with allow and block lists or attribute-based (ABAC) policies on agents, LLM services, and MCP servers.

Access rules decide who can use a resource. Which tool calls need approval is a separate control. See Tool approval and credentials.

Rules at a glance​

WhatWhere you set itRestrictsLicense
Who can use an agentAgent editor, Access tab, User accessUsers and teamsProfessional for allow and block lists, Enterprise Advanced for attribute-based
Where an agent worksAgent editor, Access tab, Channel accessChannelsProfessional
Who can edit an agentAgent admins, manage_own_agent, manage_others_agentManagersNone. See Create and manage agents.
Who can use an LLM serviceService panel, Access policyUsersEnterprise Advanced
Who can use an MCP serverMCP Configuration tab, Access policyUsersEnterprise Advanced
Where an agent auto-repliesChannel settings, Agents tabChannelEnterprise Advanced. See Use agents in channels.

Allow and block lists​

On an agent's Access tab:

  • User access: Allow for all users (default), Allow for selected users, Block selected users, or Attribute-based (access policy). Selected-user lists take individual users and whole teams. Team membership is checked when the person uses the agent.
  • Channel access: Allow for all channels (default), Allow for selected channels, Block selected channels, or Block all channels. Block all channels makes the agent direct-message only.

The server enforces these rules for @mentions, direct messages, slash commands, and tool-driven access. Channel rules don't apply to direct messages. Creating an agent with restrictions needs a Professional license. Opening an agent back up to everyone, and editing an existing list, work at any license level.

Attribute-based access control​

Attribute-based access control (ABAC) restricts access with policies written against user attributes, for example user.attributes.department == "engineering". You don't maintain user or team lists. A policy always grants or denies the use action on one resource.

Requirements:

  • An Enterprise Advanced license.
  • Attribute-based access control enabled on the Mattermost Server. The plugin checks, and hides all ABAC settings when the server doesn't offer it.
  • User attributes (custom profile attributes) configured, because policies refer to them.

Policies for each resource​

ResourceWhere you author itBehavior
AgentAgent editor, Access tab. Set User access to Attribute-based (access policy), save, then define the policy.The policy is the only user gate. The agent's allow and block lists are ignored.
LLM serviceSystem Console > Plugins > Agents, on the service panelRestricts every agent that uses the service, on top of each agent's own rules. The policy also affects who can see the service and its agents.
MCP serverSystem Console > Plugins > Agents > Model Context Protocol (MCP), Configuration tab. Built-in and plugin servers are under Built-in & plugin servers.Applies to remote servers, the built-in Mattermost MCP server, and plugin-registered servers. Users who are denied lose that server's tools without notice.

Denying the built-in Mattermost MCP server removes nearly all Mattermost tools for the users it matches.

Each editor has Simple and Advanced modes. Advanced takes a CEL expression, and is for System Admins. If a policy uses an expression the simple editor can't show, only a System Admin can edit it, and anyone who can manage the agent can remove it. The editor warns you if the policy would exclude you.

Who can author:

PolicyWho
Agent policyThe agent's creator, its agent admins, and users with manage_others_agent. While Use service accounts for authentication is on, only System Admins.
Service policySystem Admins
MCP server policySystem Admins

How a request is decided​

  • No policy on a service or MCP server: unrestricted. Installing or upgrading the plugin changes nothing until you write a policy.
  • No policy on an agent in attribute-based mode: everyone is denied. Define the policy right after you switch the mode. This also applies after a version restore. See Create and manage agents.
  • A policy exists: it decides. Matching users are allowed, others are denied.
  • An evaluation fails: the request is denied for every agent, service, and MCP server. If the server reports that no policy exists, agents in a legacy mode use their allow and block lists.
  • Server without ABAC: legacy agents keep their lists, and services and MCP servers are unrestricted. Agents in attribute-based mode are unusable for everyone until you upgrade or change the mode.

The access tab's hint says "Until a policy is defined, all users can use this agent." That doesn't match the server, which denies. Define a policy first.

Visibility​

Lists and pickers show only what a user can use, with two exceptions. System Admins can see services and the agents that use them even when a service policy denies them, so they can audit and repair bindings. An agent's creator and agent admins can see the agent even when its agent policy denies them. A service policy that denies them still hides the agent. Everyone else doesn't see agents or services they can't use. Agents denied by a policy don't show as Inactive. They're absent. If an agent admin loses service access, they can't see or fix the agent. A System Admin must restore access or change the service.

Policy lifecycle​

  • Deleting an agent removes its policy.
  • Deleting a service or an MCP server from the configuration doesn't delete its policy. If you recreate a resource with the same ID, the old policy applies again. Remove the policy first if you don't want that.
  • A plugin MCP server's policy is tied to the plugin ID. It survives unregistering, and reattaches if the same plugin registers again.
  • Policy changes are recorded in the audit log. See Monitor Agents.