MCP tool calls slow and intercepted/wiretapped?
Open 💬 4 comments Opened Apr 6, 2026 by codengine
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
0.117.0 & 0.118.0
What subscription do you have?
Pro
Which model were you using?
gpt-5.4
What platform is your computer?
_No response_
What terminal emulator and version are you using (if applicable)?
_No response_
What issue are you seeing?
Starting with 0.117.0, MCP tool calls are very slow. Sometimes they get blocked by some security mechanisms that seem to inspect the tool calls (it reads as "the users intention was too.... so it was blocked). I understand why such guardrails are important, but this has some inconvenient implications.
- The agent is confused
- MCP tool calls are much, much slower than with 0.116.0
I switched back to 0.116.0 and the speedup was immediately noticable.
What steps can reproduce the bug?
Use an MCP server (I used ida-pro-mcp) and just let the agent work with it.
What is the expected behavior?
- MCP calls are not intercepted
- MCP calls are as fast as they were with 0.116.0
Additional information
_No response_
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I've had this yesterday and today when it called supabase mcp it keeps hallucinating to run web.run and keeps saying "sorry" or "mistake" i just did a new session and it fixed itself.
I'm using GPT 5.2 xhigh
@etraut-openai could you please prioritize this ticket? It's a blocker for me whenever 0.116.0 stops to work at May 8th as per the on-CLI announcement.
Could we have an update here please? This is really a problem - MCP tool calls are crawling right now, it's orders of magnitudes slower because of the round-trips through your servers/audits.