New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

codex_fresh_eyes

Run /codex fresh-eyes through local Codex OAuth/session using MCP context resources.

SERVERNogra SOURCE@nograai/mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-nograai-nogra-mcp/codex-fresh-eyes.md

What codex_fresh_eyes does on Nogra

AI agents invoke codex_fresh_eyes to trigger actions in Nogra. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why codex_fresh_eyes is rated High

The tool performs code execution ('Run /codex fresh-eyes') via a local Codex service with session-based authentication. This is an Execute category tool because it runs an external operation whose side effects depend on what the fresh-eyes command does and how it is invoked. While the actual impact depends on the codex service's capabilities, the tool itself is designed to execute commands.

From the tool's definition Tool description states 'Run /codex fresh-eyes' which is a direct invocation of an external command/operation.

Questions about codex_fresh_eyes

What does the codex_fresh_eyes tool do? +

Run /codex fresh-eyes through local Codex OAuth/session using MCP context resources. It is categorised as a Execute tool in the Nogra MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on codex_fresh_eyes? +

Register the Nogra MCP server in PolicyLayer and add a rule for codex_fresh_eyes: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Nogra. Nothing to install.

What risk level is codex_fresh_eyes? +

codex_fresh_eyes is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit codex_fresh_eyes? +

Yes. Add a rate_limit block to the codex_fresh_eyes rule in your PolicyLayer 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.

How do I block codex_fresh_eyes completely? +

Set action: deny in the PolicyLayer policy for codex_fresh_eyes. 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.

What MCP server provides codex_fresh_eyes? +

codex_fresh_eyes is provided by the Nogra MCP server (@nograai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Nogra, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nogra's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.