[aw] Smoke Copilot Network Isolation is missing required tool

[github-actions]

Workflow Failure

Workflow: Smoke Copilot Network Isolation
Branch: copilot/refactor-sbx-manager-tests
Run: https://github.com/github/gh-aw-firewall/actions/runs/36337338142
Pull Request: #9078

Warning

Missing Tools Reported: The agent reported missing tools during execution.

Missing Tools:

• bash/curl execution: bash tool denied executing curl commands ("Permission denied and could not request permission from user") for both egress checks, preventing verification of allow/deny network isolation behavior.

Alternatives:

Tool	Alternative
bash/curl execution	Re-run workflow with bash tool permissions enabled, or manually run the two curl commands inside the sandbox and report results.

Warning

Engine Failure: The copilot engine terminated unexpectedly.

Last agent output:

● add_comment (MCP: safeoutputs) · body: "@lpcox Unable to complete smoke test — the bash tool deni…
  └ {"result":"success","temporary_id":"aw_rdA0EAKV","comment":"#aw_rdA0EAKV...
[safeoutputs-cli] hasTerminalSafeOutput: terminal entry found in /home/runner/work/_temp/gh-aw/safeoutputs/outputs.jsonl: type=add_comment
Both required curl checks were blocked by the sandbox before any network activity occurred ("Permission denied and could not request permission from user"), so no genuine egress verdict could be obtained. I reported this via `missing_tool` and posted a comment noting the inconclusive FAIL result with the required `EGRESS_RESULT` line.
Changes   +0 -0
Duration  16s
Tokens    ↑ 203.9k • ↓ 908 • 162.6k (cached)
Run 'docker run --help' for more information
Run 'docker run --help' for more information
Run 'docker run --help' for more information

Action Required

Assign this issue to an agent to debug and fix the issue.

Debug with any coding agent

Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):

Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/github/gh-aw-firewall/actions/runs/36337338142

Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

• Start your agent
• Load the agentic-workflows skill from .github/skills/agentic-workflows/SKILL.md or https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.md
• Type debug the agentic workflow smoke-copilot-network-isolation failure in https://github.com/github/gh-aw-firewall/actions/runs/36337338142

Tip

Stop reporting this workflow as a failure

To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:

safe-outputs:
  report-failure-as-issue: false

Generated from Smoke Copilot Network Isolation · copilot · 14.5 AIC · ◷

• expires on Oct 4, 2026, 5:36 PM UTC

[github-actions]

Agent job 36337444861 failed.

Warning

Missing Tools Reported: The agent reported missing tools during execution.

Missing Tools:

• bash network egress (curl): Bash tool blocked curl network commands with 'Permission denied' before execution (sandbox policy), so the two egress checks (allow api.github.com / deny example.com) could not be run to produce real EGRESS_RESULT data.

Alternatives:

Tool	Alternative
bash network egress (curl)	Re-run the smoke test in an environment where the bash tool permits outbound curl calls, or run the two curl commands manually and report EGRESS_RESULT.

Warning

Engine Failure: The copilot engine terminated unexpectedly.

Last agent output:

● add_comment (MCP: safeoutputs) · body: "@lpcox Smoke test could not run: the bash tool blocked bo...
  └ {"result":"success","temporary_id":"aw_wNaGQlEC","comment":"#aw_wNaGQlEC...
[safeoutputs-cli] hasTerminalSafeOutput: terminal entry found in /home/runner/work/_temp/gh-aw/safeoutputs/outputs.jsonl: type=add_comment
I couldn't execute the two curl egress checks — the bash tool rejected them with "Permission denied and could not request permission from user" before any network call was attempted, so no real AWF egress data could be gathered (even `echo hello` worked, confirming it was network commands specifically being blocked). I reported this via `missing_tool` and posted a PR comment with `EGRESS_RESULT allow=fail deny=fail` reflecting that the checks did not run, tagging the PR author.
Changes   +0 -0
Duration  30s
Tokens    ↑ 288.3k • ↓ 1.3k • 246.5k (cached)
Run 'docker run --help' for more information
Run 'docker run --help' for more information
Run 'docker run --help' for more information

Generated from Smoke Copilot Network Isolation · copilot · 16.7 AIC · ◷