Tool approval and credentials
Only the person who started a conversation can approve an agent's tool calls, and tools run with that person's credentials. This page is for admins and security reviewers. To see what to click, read Use tools and approve actions.
Roles
The initiator is the person who mentioned the agent or wrote in a direct message or Agents pane thread. The initiator is the executor: tools run as them, unless the agent uses a service account. Anyone else who can read the channel is an observer. Observers can't approve, and by default can't see tool arguments or private results. Roles don't change mid-conversation.
Whose credentials run a tool
An agent runs tools in one of two modes. The mode is a setting on the agent, not a per-call choice.
Per-user authentication (default). Tools run as the initiator.
- Mattermost tools use the initiator's user record, channel memberships, and team memberships. They see only what the initiator can see.
- OAuth-backed MCP servers use the initiator's own token. Two people running the same tool can get different results, because they have different scopes. A call can succeed for one and fail with a 401 or 403 for the other. A 401 from an MCP server prompts the initiator to authorize again.
- The agent's bot account never runs third-party tools. It only posts the reply and tool cards.
- For an MCP server without OAuth, the server's own configured credential decides what the call can do. The initiator rule still decides whether the call happens.
Service account authentication. External MCP servers get shared credentials, while Mattermost and plugin tools still run as the initiator. The initiator still approves each call. See Service account authentication.
Approval policies
Admins set a policy for each tool on the Tools tab of the MCP settings. The agent's tool grants decide what the agent may use. They never change the policy.
| Policy (System Console label) | Stored value | Behavior |
|---|---|---|
| Ask Every Time | ask | The initiator must accept every call, in direct messages and channels. |
| Auto Run (DM) | auto_run_in_dm | Runs without a prompt in a direct message with the agent. In channels it asks. |
| Auto Run (Everywhere) | auto_run_everywhere | Runs without a prompt in direct messages and channels. |
A tool with no stored setting is enabled and set to ask. Tools are off in channels unless an admin turns on Enable Channel Mention Tool Calling, which is experimental. See Control agents in channels. Per call, the server decides like this:
| Conversation | Policy ask | Policy auto_run_in_dm | Policy auto_run_everywhere |
|---|---|---|---|
| Direct message | Ask | Run | Run |
| Channel | Ask | Ask | Run |
Some tools have no policy:
search_toolsandload_tool, the dynamic loading helpers, always run without approval.- The built-in
CreateFiletool always runs without approval, because it only attaches a file to the agent's own reply.wait_for_async_work, which schedules the agent's own follow-up, does too. AskUserQuestionalways waits for the user's answer.- The built-in web search tool (Brave, Google, or SearXNG) always asks. Native provider web search runs inside the provider, so it has no approval card.
Choose a policy
- Use Ask Every Time for any tool that writes data, sends notifications, costs money, or returns something the initiator shouldn't see without consent. It's the safe default.
- Use Auto Run (DM) for read-only tools whose results are fine in a private conversation but might leak context in a shared channel. Examples: search the initiator's own mail, list their calendar. Mattermost seeds its own read-only tools at this level.
- Use Auto Run (Everywhere) only for read-only tools whose results are safe for every channel member, and that enforce per-user permissions themselves. Tools that call external APIs rarely qualify. Results of these tools are shared with the channel at once, with no per-call privacy choice.
- A policy only decides whether the user is asked. Limit what a tool can do with OAuth scopes and least-privilege service accounts.
Policies below Enterprise
Setting a policy that runs tools automatically needs an Enterprise license. Below Enterprise, Mattermost's own tools use the product defaults described in Connect agents to MCP servers, and every other tool asks. A stricter policy you stored earlier still applies, and a disabled tool stays disabled. Remote MCP tools don't run at all below Enterprise.
Approval rules
- Only the initiator can accept or reject a pending call. The server checks that the clicking user is the conversation's recorded initiator and rejects any other request before a tool runs. An admin can't approve someone else's call. Admins control approval only by setting the tool's policy.
- A pending call that nobody answers stays pending. It never approves itself or moves to someone else, and nothing runs. Starting a new conversation creates a new initiator.
- A reply can mix automatic and pending tools. Automatic ones show an Auto-approved badge. Pending ones keep Accept and Reject. When several calls are pending, Accept all and Reject all follow the same initiator-only rule.
- No other channel member, channel admin, or System Admin can approve. For an OAuth-backed MCP server, a call fails if the user's token is missing or rejected, and never falls back to the bot or a shared credential.
Share or keep private
In a channel, after an approved call returns, the initiator chooses Share or Keep private. See Use tools and approve actions. Admin-relevant facts:
- The decision is recorded once, and there's no unshare.
- Tools set to Auto Run (Everywhere) skip this step and are shared immediately.
- Direct messages skip it, because only the initiator is there.
What observers see
| Observers see | Observers don't see |
|---|---|
| The agent's written reply | Tool arguments, which are replaced by a placeholder while a call is pending or kept private |
| The tool name | The result of any tool the initiator kept private |
| An Auto-approved badge | Working Accept and Reject buttons |
| The follow-up built from shared content | Anything the agent wrote from private results that would reveal them |
Automated triggers
A post written by a bot, plugin, or OAuth app has no human who can approve.
- Webhook posts never trigger an agent. Bot and plugin posts do only when they set the
activate_aipost property. - A bot post that sets
activate_aican start a channel turn. With channel tool calling on, Mattermost removes every tool except those set to Auto Run (Everywhere) and the built-in helpers. With it off, the run has no tools. - Any other automated post starts a run with no tools.
There's no path where a bot approves its own call. To let an automated flow use a tool, set that tool to Auto Run (Everywhere) after a security review, or keep a person in the loop.
Audit
In-channel approvals are recorded in the server audit log as toolCallApproval and toolResultApproval, with identifiers only. See Monitor Agents.