Review code changes from a diff using AI-powered analysis. This tool performs a structured code review on a unified diff, identifying issues across correctness, security, performance, maintainability, style, and documentation. Key Features: - Structured output with findings, priority levels (P0-P...
AI agents call review_changes to retrieve information from Context Engine MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and analyzes a provided diff, producing a structured review report with findings and suggestions. It does not modify code, execute commands, delete data, or move money. It is essentially a read/analysis operation on input data. Severity is medium because a misconfigured or manipulated review could suppress critical security findings or mislead an agent into merging harmful code.
From the tool's definition Review code changes from a diff using AI-powered analysis... performs a structured code review on a unified diff, identifying issues
Documented attack patterns abuse exactly the kind of access review_changes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Context Engine MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for review_changes:
{
"version": "1",
"default": "deny",
"tools": {
"review_changes": {}
}
}review_changes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Review code changes from a diff using AI-powered analysis. This tool performs a structured code review on a unified diff, identifying issues across correctness, security, performance, maintainability, style, and documentation. Key Features: - Structured output with findings, priority levels (P0-P3), and confidence scores - Changed lines filter: focuses on modified code (can be toggled) - Confidence scoring: each finding has a 0-1 confidence score - Actionable suggestions: includes fix suggestions where applicable Priority Levels: - P0 (Critical): Must fix before merge - bugs, security vulnerabilities - P1 (High): Should fix before merge - likely bugs, significant issues - P2 (Medium): Consider fixing - code smells, minor issues - P3 (Low): Nice to have - style issues, minor improvements Categories: - correctness: Bugs, logic errors, edge cases - security: Vulnerabilities, injection risks, auth issues - performance: Inefficiencies, memory leaks, N+1 queries - maintainability: Code clarity, modularity, complexity - style: Formatting, naming conventions - documentation: Comments, docstrings, API docs Output Schema: Returns JSON with: findings[], overall_correctness, overall_explanation, overall_confidence_score, changes_summary, and metadata. Usage Examples: 1. Basic review: Provide diff content 2. Focused review: Set categories=. It is categorised as a Read tool in the Context Engine MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Context Engine MCP Server MCP server in PolicyLayer and add a rule for review_changes: 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 Context Engine MCP Server. Nothing to install.
review_changes 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_changes 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_changes. 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_changes is provided by the Context Engine MCP Server MCP server (kirachon/context-engine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Context Engine MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
50 Context Engine MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.