---
title: "corestack_firewall_change_get"
url: https://docs.corefinity.com/mcp/tools/corestack_firewall_change_get
type: tool
last_updated: 2026-11-13
feature: firewall
related:
  - https://docs.corefinity.com/api/reference/firewall/get-firewall-change.md
  - https://docs.corefinity.com/guides/sites/access-and-security/firewall.md
---
# corestack_firewall_change_get

**Show a firewall change.** Show how far a firewall change has got: applying, applied, failed (with each environment it has not reached yet) or recorded. Scope: read.

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

## When to use it

Follow a firewall change: `applying`, `applied`, `failed` (each environment not reached yet, with its reason — it is retried) or `recorded` (nothing to apply yet: the environments' firewall is not enforced).

## Inputs

- `change_id` (integer, required)

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "change_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "change_id"
  ],
  "type": "object"
}
```

## Refusals

- 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).
- `switched_off`: the firewall is not available for this object yet.

## Example

```json
{
  "name": "corestack_firewall_change_get",
  "arguments": {
    "change_id": 777
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_firewall_change_get with change_id 777. (Show a firewall change.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [GET /api/firewall/changes/{change}](https://docs.corefinity.com/api/reference/firewall/get-firewall-change.md)
- Guide: [Firewall](https://docs.corefinity.com/guides/sites/access-and-security/firewall.md)
