---
title: "corestack_nginx_rules_revision_get"
url: https://docs.corefinity.com/mcp/tools/corestack_nginx_rules_revision_get
type: tool
last_updated: 2026-11-13
feature: nginx-rules
related:
  - https://docs.corefinity.com/api/reference/site-settings/get-site-nginx-revision.md
  - https://docs.corefinity.com/guides/sites/site-settings/web-server-rules.md
---
# corestack_nginx_rules_revision_get

**nginx rules revision.** Read one nginx rules revision of an environment row: its four hooks and a unified diff per hook against another revision (default the current one); with include_errors, the web error lines logged since it went live. Scope: read.

- Scope: `read`
- Runs as a task: no

## When to use it

Read one nginx rules revision of an environment row: its four hooks and a unified diff per hook against another revision (default the current one); with include_errors, the web error lines logged since it went live.

The answer: `revision` (its history row and `content` per hook), `against` (`id`, `current`) and `diff` per hook (null where the hook agrees). With `include_errors`, `errors`: `available` (false with a `reason` when the environment's logs cannot be read or the revision never went live), `count` (every line in the range), `from` (never older than the logs keep), `to` and up to 50 `lines` (`at`, `level`, `message`).

## Inputs

- `site_id` (integer, ≥ 1, required): The environment row.
- `revision_id` (integer, ≥ 1, required): The revision (an id from corestack_nginx_rules_history_list).
- `against_revision_id` (integer, ≥ 1): Diff against this revision of the row instead of the current one.
- `include_errors` (boolean): Also the web error lines since the revision went live (up to 50).

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "against_revision_id": {
      "description": "Diff against this revision of the row instead of the current one.",
      "minimum": 1,
      "type": "integer"
    },
    "include_errors": {
      "description": "Also the web error lines since the revision went live (up to 50).",
      "type": "boolean"
    },
    "revision_id": {
      "description": "The revision (an id from corestack_nginx_rules_history_list).",
      "minimum": 1,
      "type": "integer"
    },
    "site_id": {
      "description": "The environment row.",
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "site_id",
    "revision_id"
  ],
  "type": "object"
}
```

## Refusals

- `feature_off`: `include_errors` while logs are not available yet.
- The refusals every tool can answer: `invalid_arguments`, `tenant_mismatch`, `scope_required`, `pin_refused`, `rate_limited`, `temporarily_unavailable`, `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_nginx_rules_revision_get",
  "arguments": {
    "site_id": 4211,
    "revision_id": 812,
    "include_errors": true
  }
}
```

## Path apps

The answer also carries the revision's path apps: `revision.content.path_apps` (its records and gates, the whole list as corestack_nginx_rules_update takes it; null when it had none) and `diff.path_apps`, a unified diff of the two lists written as YAML against the revision named by `against` (null where they agree).

## Prompt

```text
Using the Corefinity MCP server, call corestack_nginx_rules_revision_get with site_id 4211, revision_id 812, include_errors true. (nginx rules revision.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [GET /api/corestack/sites/{site}/nginx-rules/revisions/{revision}](https://docs.corefinity.com/api/reference/site-settings/get-site-nginx-revision.md)
- Guide: [Web server rules](https://docs.corefinity.com/guides/sites/site-settings/web-server-rules.md)
