Skip to content

Fix test-proxy.md to use automatic comment creation instead of manual GitHub tools #190

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Mossaka merged 3 commits into from
Aug 27, 2025
Merged

Fix test-proxy.md to use automatic comment creation instead of manual GitHub tools #190

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d9a8f37
Update test-proxy.md to use comments instead of creating issues
Copilot Aug 22, 2025
f048c8d
changed the instruction to comment on PR instead of raising a new issue
Mossaka Aug 22, 2025
6e0a957
Remove create_comment tool and add inline PR number as requested in r…
Copilot Aug 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
113 changes: 106 additions & 7 deletions .github/workflows/test-proxy.lock.yml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

16 changes: 9 additions & 7 deletions .github/workflows/test-proxy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,8 @@ on:
branches: [ "main" ]
workflow_dispatch:

permissions:
issues: write # needed to write the output report to an issue
output:
issue_comment: {}

tools:
fetch:
Expand All @@ -21,8 +21,6 @@ tools:

github:
allowed:
- "create_issue"
- "create_comment"
- "get_issue"

engine: claude
Expand All @@ -44,10 +42,14 @@ Test the MCP network permissions feature to validate that domain restrictions ar
- Verify that all blocked requests fail at the network level (proxy enforcement)
- Confirm that only example.com is accessible through the Squid proxy

Create a GitHub issue with the test results, documenting:
## Reporting Instructions

If there are any failures, security issues, or unexpected behaviors:

- Write a detailed report to ${{ env.GITHUB_AW_OUTPUT }} documenting:
- Which domains were successfully accessed vs blocked
- Error messages received for blocked domains
- Confirmation that network isolation is working correctly
- Any security observations or recommendations
- Specific failure details that need attention

The test should demonstrate that MCP containers are properly isolated and can only access explicitly allowed domains through the network proxy.
The test results will be automatically posted as a comment on PR #${{ github.event.pull_request.number }}.