Terms
- Read tools: fetch data, such as logs, workflow history, or pull requests. Read tools don’t take any actions.
- Write tools: tools that let Resolve perform actions in an integration, including tools that delete. Each integration page lists its tools under Tools.
- Tool permissions: the setting for each tool, Blocked, Needs approval, or Always allow, plus who the tool runs as.
- Action: one use of a write tool.
- Action History: an audit trail of the actions Resolve has run. Only admins can see it.
Permissions
Each configurable tool on an integration has one of three permissions:
You can configure every tool of an MCP integration, and every write tool of built-in integrations such as Temporal or GitHub, one tool at a time or a whole group at once. You can’t configure the read tools of built-in integrations: Resolve can always use them.
Set permissions under Tool permissions on each integration’s page in Resolve, under Integrations. Only admins can change the organization default and team overrides. Permissions apply at three levels:
- Organization default: applies to every team and Task.
- Team overrides: change any configurable tool for one team.
- Task overrides: change a tool for one Task.
Team overrides
Use team overrides when one team needs different settings, for example to let the team that owns a service run its deploys without approval.- Turn a team off to remove its access to the integration. Resolve can’t use any of the integration’s tools when it works for that team.
- For a team that’s on, change the permission of any configurable tool for that team, to stricter or looser than the organization default. Tools you don’t change follow the organization default.
- Teams with overrides are listed first, under how many teams differ from the organization default. The rest follow the organization default.
Task overrides
A Task can set its own permission for a tool. A Task member can only make a tool stricter than what the team or organization allows. An admin can also make it looser.How Resolve tells MCP read tools from write tools
Resolve checks each tool of an MCP integration itself. ResolveAI reads the tool’s name, description, and input parameters, and judges the most a single call to the tool could do:- Read tool: only reads, searches, or runs queries that can’t change data, such as PromQL or JQL.
- Write tool: can create, change, delete, or send something, such as adding a comment, creating a ticket, or paging someone.
- If the model isn’t confident in its answer, or gives none, the tool counts as a write tool.
- Until a tool has been checked, it counts as a write tool.
How an action runs
- Resolve decides an action would help and requests it, with the reason and the exact change. Resolve never requests a tool set to Blocked.
- Resolve checks the tool’s permission:
- Needs approval: the request waits on an approval card in the web app, Slack, or Microsoft Teams. If a person approves it, the action runs. If they reject it, nothing changes.
- Always allow: the action runs without waiting for anyone.
- The action runs as whoever the tool’s Runs as setting names: Resolve, using the integration’s shared credentials, or the approver, using their own account. See Credentials.
- The request, the decision, and the result are recorded in Action History.
Turn on write tools
Integrations are read-only until you give them write access. Follow the steps on the integration’s page. This usually means credentials with write access, and sometimes a setting on the connection. Then set each write tool’s permission on the integration’s page in Resolve.Credentials
By default, an action runs with the integration’s shared credentials. On App for GitHub, an action that needs approval can instead run as the person who approves it. The action can do only what both the GitHub App and the approver are allowed to do: the app’s permissions on the repositories it’s installed on, and the approver’s own access to those repositories.- The approver signs in to GitHub, through GitHub’s standard OAuth sign-in, the first time they approve. Approving from Slack or Teams opens Resolve in the browser to do this.
- Resolve gets a GitHub App user token for the approver.
- The token is stored encrypted for at most 8 hours. Resolve doesn’t keep refresh tokens.
- If the approver hasn’t connected GitHub, the action doesn’t run. Resolve never falls back to shared credentials.
- If GitHub refuses the approver, nothing changes and the request is recorded as denied.
- An action whose tool is set to Always allow always uses shared credentials.
- Per-user credentials work on github.com only.
Limit what Resolve can reach
- Resolve can change only what the integration’s credentials allow.
- Some integrations have their own switch. For example, Temporal writes only to connections that set
allowWrites. - Blocked keeps Resolve from using a tool at all, for the whole organization or for one team or Task.

