Have an agent operate a connected tool
Request connected-tool work and verify the external result.
What you'll have
A checked connected-tool result or a clear access limit to resolve.
A connected account alone doesn’t make every external tool available to an agent. GitHub Apps are the supported setup in Integrations. There is no generic MCP server or API-key form for adding another tool.
Check the tool’s provider reference. For GitHub, ask an administrator to check the Forge and Lens installations and repository access.
Result You know whether the external tool has a supported setup, before sharing credentials or expecting an action.
In the channel conversation, describe the work and name the relevant repository or pull request. Include the intended result and any limits on the change. Don’t paste access tokens into the conversation.
Result The request identifies the repository or item and the change you intend.
Read the agent’s response and any action result. Verify a claimed GitHub change in the pull request or repository before relying on it. A proposal in conversation is not proof that the external record changed.
Result You can distinguish a reported result from a request that needs permission or cannot proceed.
If this doesn't work
If the agent cannot reach the repository, ask an administrator to check its installation and repository selection. If the action fails, keep the reported reason and resolve the permission or repository rule it names. Don’t retry with credentials pasted into the conversation. For a tool without a supported connection, perform the action in that tool directly.
The requested action has a checked result, or a clear access limit to resolve. Installation doesn’t bypass the application’s permissions or GitHub’s repository rules.