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

**nginx snippets.** The nginx snippet library for an environment row's platform: each snippet's parts (hook, content, placement) and placeholders, whether the row can use it now, and otherwise which hooks or capabilities it waits for (the one-time update). Insert every part of a snippet into one corestack_nginx_rules_update. Scope: read.

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

## When to use it

The nginx snippet library for an environment row's platform: each snippet's parts (hook, content, placement) and placeholders, whether the row can use it now, and otherwise which hooks or capabilities it waits for (the one-time update). Insert every part of a snippet into one corestack_nginx_rules_update.

The rate-limit snippets (`rate-limit-*`) are listed only for an environment whose runtime supports the platform rate-limit presets; on any other they are left out rather than shown as waiting.

## Inputs

- `site_id` (integer, ≥ 1, required): The environment row.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "site_id": {
      "description": "The environment row.",
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "site_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).

## Example

```json
{
  "name": "corestack_nginx_snippets_list",
  "arguments": {
    "site_id": 4211
  }
}
```

## Path apps

The list also holds the path app presets: entries with `category` `path-apps` and `kind` `path_app`, whose `preset` holds the record fields they pre-fill (WordPress admin for FishPig, WordPress full, legacy PHP directory, static directory, another site (proxy), single PHP entry, IP or host gate). They have no nginx parts: add the record to `path_apps` in corestack_nginx_rules_update (with its `preset` key), filling in what the preset leaves to you, such as a legacy directory's PHP files, a gate's addresses or another site's `proxy.url`. The `proxy-site` preset is listed whether or not this environment's runtime takes a proxy yet; corestack_nginx_rules_get's `path_apps.proxy_available` says whether it does.

## Prompt

```text
Using the Corefinity MCP server, call corestack_nginx_snippets_list with site_id 4211. (nginx snippets.) Tell me what it returned.
```

## The same task elsewhere

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