Send a prompt to OpenAI Codex CLI (defaults to gpt-5.4 with automatic fallback on quota errors). Use for code review, second opinions, analysis, and AI-to-AI collaboration. Do not override the model parameter unless the user explicitly asks. Returns both human-readable text and a structured respo...
Part of the Ask Codex MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call ask-codex to retrieve information from Ask Codex without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though ask-codex only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
ask-codex:
rules:
- action: allowSee the full Ask Codex policy for all 3 tools.
Agents calling read-class tools like ask-codex have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Send a prompt to OpenAI Codex CLI (defaults to gpt-5.4 with automatic fallback on quota errors). Use for code review, second opinions, analysis, and AI-to-AI collaboration. Do not override the model parameter unless the user explicitly asks. Returns both human-readable text and a structured response (provider, model, sessionId, usage) via outputSchema. The returned sessionId field maps to Codex's thread_id and can be passed back as sessionId to continue the conversation.. It is categorised as a Read tool in the Ask Codex MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for ask-codex. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ask Codex MCP server.
ask-codex is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ask-codex rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the Intercept policy for ask-codex. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
ask-codex is provided by the Ask Codex MCP server (ask-codex-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept