Document role requirements for audit/logs tools in agentic-workflows#15194
Merged
Document role requirements for audit/logs tools in agentic-workflows#15194
Conversation
Copilot stopped work on behalf of
pelikhan due to an error
February 12, 2026 15:40
Copilot stopped work on behalf of
pelikhan due to an error
February 12, 2026 15:40
Copilot stopped work on behalf of
pelikhan due to an error
February 12, 2026 15:40
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
…s tool Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Document roles requirement for audit/logs tool access
Document role requirements for audit/logs tools in agentic-workflows
Feb 12, 2026
pelikhan
approved these changes
Feb 12, 2026
This was referenced Feb 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
auditandlogstools in the agentic-workflows MCP server require write+ repository access, but this was undocumented. Users with read/triage roles would encounter permission denied errors without understanding why.Changes
Setup Guide (
setup/mcp-server.md):logsandaudittool descriptionsReference Documentation:
permissions.mdto note role requirements for audit/logs toolstools.mdwith role requirement notice in Agentic Workflows sectionPermission Requirements
Runtime validation uses GitHub API:
GET /repos/{owner}/{repo}/collaborators/{username}/permissionWarning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
telemetry.astro.build/opt/hostedtoolcache/node/24.13.0/x64/bin/node node /home/REDACTED/work/gh-aw/gh-aw/docs/node_modules/.bin/astro build(dns block)/opt/hostedtoolcache/node/24.13.0/x64/bin/node node /home/REDACTED/work/gh-aw/gh-aw/docs/node_modules/.bin/astro build ocs/examples/multi-repo/feature-53 ocs/�� ocs/examples/manual.md ocs/examples/multi-repo.md ocs/examples/scheduled.md ocs/examples/comsh ocs/examples/iss-c ocs/examples/agenode install.js ocs/setup/creating-workflows.mdx ocs/�� ocs/setup/mcp-server.md ocs/setup/cli.md bin/git(dns block)If you need me to access, download, or install something from one of these locations, you can either:
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.