Request a code review of all files in a directory from Codex and Gemini CLIs. Returns feedback from both reviewers for Claude to consider.
AI agents call review_directory to retrieve information from Review MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads files from a directory and retrieves analysis/feedback from external CLI tools (Codex and Gemini). It does not modify, delete, or execute code — it performs read-only analysis and returns results.
From the tool's definition "Request a code review of all files in a directory" and "Returns feedback from both reviewers for Claude to consider"
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Request a code review of all files in a directory from Codex and Gemini CLIs. Returns feedback from both reviewers for Claude to consider. It is categorised as a Read tool in the Review MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Review MCP Server MCP server in PolicyLayer and add a rule for review_directory: 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 Review MCP Server. Nothing to install.
review_directory 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 review_directory 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.
Set action: deny in the PolicyLayer policy for review_directory. 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.
review_directory is provided by the Review MCP Server MCP server (je4550/review-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →