/review invokes GitHub MCP tools despite explicit local-only restriction

Open 💬 1 comment Opened May 5, 2026 by alex-rosenberg35

What version of Codex CLI is running?

0.128.0

What subscription do you have?

ChatGPT Pro (5x)

Which model were you using?

gpt-5.5

What platform is your computer?

Linux 6.17.0-19-generic x86_64 x86_64

What terminal emulator and version are you using (if applicable)?

_No response_

What issue are you seeing?

The /review workflow now calls GitHub MCP connector tools, such as codex_apps.github_list_repositories, even when I explicitly say that GitHub MCP tools are not allowed and the review must use only the local shell and git CLI.

This is a behavior change. /review previously did not invoke GitHub MCP tools for local repository review.

What steps can reproduce the bug?

Uploaded thread: 019df92d-4b2d-74b3-87cb-db4b5332dd96

What is the expected behavior?

When a user prohibits GitHub MCP tools, /review should honor that constraint and perform the review using only local filesystem access, shell commands, and git CLI.

Additional information

I repeatedly stated that GitHub MCP tools were not allowed. Despite that, the review flow attempted to use GitHub MCP tooling. This creates a trust and privacy issue because repository review may unexpectedly access connected GitHub integrations when the user requests local-only operation.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗