---
title: "Review and guardrails"
description: "How Overlane reviews pull requests, how guardrail rules stop agents server-side, and where secret scanning and the code map fit."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.overlane.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Review and guardrails

Overlane reviews pull requests and enforces your rules on the server, so an agent that ignores its instructions still cannot cross them. Deterministic checks come first (a secret scan, static rules and diff validation); a model pass is optional and comes second.

- [How review works](/review/how-review-works/): the deterministic checks, the optional model pass, findings, the summary, token caps, forks, learning and what is sent to model providers.
- [Guardrail rule files](/review/guardrail-rules/): policy as code for tools, paths, spend, egress and deploys.
- [Dry-run and approvals](/review/dry-run-and-approvals/): see what a rule would block, and have an independent agent approve an action before it runs.
- [Secret scanning](/review/secret-scanning/): what blocks and what is only reported.
- [Code-map defaults](/review/code-map-defaults/): where the code map is on, and why.
- [Project wiki](/review/project-wiki/): a private wiki of pages generated from the code map, one for each package or app.
- [How Overlane uses models](/review/how-overlane-uses-models/): the rules, decision model, generative model ladder, what is sent and what is kept.

```sh
overlane review status
overlane guard rules list
overlane code-map status
```

Command reference: [review run](/cli/review-run/), [review status](/cli/review-status/), [guard check](/cli/guard-check/), [guard dry-run](/cli/guard-dry-run/), [guard rules test](/cli/guard-rules-test/) and [code-map status](/cli/code-map-status/).

Source: https://docs.overlane.app/review/index.mdx