---
title: "corestack_site_cloudflare_ssl_rule_set"
url: https://docs.corefinity.com/mcp/tools/corestack_site_cloudflare_ssl_rule_set
type: tool
last_updated: 2026-11-13
feature: cloudflare
related:
  - https://docs.corefinity.com/api/reference/domains/update-site-cloudflare-ssl-rule.md
  - https://docs.corefinity.com/guides/sites/go-live/cloudflare-for-a-site.md
---
# corestack_site_cloudflare_ssl_rule_set

**Set SSL for some of a site's domains in Cloudflare.** Set the SSL/TLS mode for some domains of a row only, with a Cloudflare Configuration Rule; the rest of the zone keeps its own mode. The domains must be the row's and in one Cloudflare zone. Scope: write.

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

## When to use it

Set the SSL/TLS mode for some domains of a row only, without changing the mode of the whole Cloudflare zone. The Control Panel adds one Cloudflare Configuration Rule that sets SSL to Full, or Full (strict), for exactly the domains named; every other name in the zone keeps the zone's own mode. Use it when one site needs Full while the zone serves other names that need something else; use `corestack_site_cloudflare_ssl_set` to change the whole zone instead.

The domains must be the row's own (as `corestack_site_cloudflare_ssl_rules_list` lists them) and all in one connected zone: set one rule for each zone. The rule acts only on traffic Cloudflare proxies. Asking for the same rule again answers the one already set. Every rule written counts against the company's Cloudflare budget of 60 changes an hour.

Needs the `write` scope.

## Inputs

- `site_id` (integer, ≥ 1, required)
- `hosts` (array of 1 to 50 domain names, required): domains of the row, all in one zone
- `ssl` (one of `full`, `strict`, required)

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "hosts": {
      "description": "Domains of the row, as corestack_site_cloudflare_ssl_rules_list lists them, all in one zone.",
      "items": {
        "maxLength": 253,
        "type": "string"
      },
      "maxItems": 50,
      "minItems": 1,
      "type": "array"
    },
    "site_id": {
      "minimum": 1,
      "type": "integer"
    },
    "ssl": {
      "enum": [
        "full",
        "strict"
      ],
      "type": "string"
    }
  },
  "required": [
    "site_id",
    "hosts",
    "ssl"
  ],
  "type": "object"
}
```

## Refusals

- `invalid_arguments` (field `hosts`): a name is not one of the row's domains, is not in a connected Cloudflare zone, or the names are in two zones; or Cloudflare refused the rule (its words are in the message). Nothing was set.
- `rules_not_allowed`: the Cloudflare token may not change the zone's Configuration Rules, or Cloudflare did not say whether it may (the Control Panel asks Cloudflare before every new rule, writing nothing). Allow Zone > Config Rules > Edit on the token, then try again. Nothing was set.
- `no_zone`: the row's domain is not in a connected Cloudflare zone, or Cloudflare is switched off for it.
- `not_connected`: connect Cloudflare for the company first, or the stored token could not be read.
- `rate_limited`: the company's Cloudflare budget for this hour is spent; `retry_after_seconds` says when to try again.
- `unavailable`: Cloudflare did not answer. When it did not confirm the rule, the answer carries it as `setting`, and the Control Panel checks it again; ask again to get it confirmed. When a rule asked for earlier could not be checked, nothing new is written beside it.
- `busy`: the same rule is being set by another request; try again in a moment.
- `deleted`, `provisioning`: the row is being deleted, or is still being created.
- `managed_elsewhere` (message: "This site is managed by another control panel"): another control panel manages this site, so use that control panel for it. Nothing was done.
- 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_site_cloudflare_ssl_rule_set",
  "arguments": {
    "site_id": 4211,
    "hosts": ["shop.example.co.uk", "www.shop.example.co.uk"],
    "ssl": "full"
  }
}
```

## Answer

- `rule`: the rule as `corestack_site_cloudflare_ssl_rules_list` shows it, `state` `active`

## Prompt

```text
Using the Corefinity MCP server, call corestack_site_cloudflare_ssl_rule_set with site_id 4211, hosts ["shop.example.co.uk","www.shop.example.co.uk"], ssl full. (Set SSL for some of a site's domains in Cloudflare.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [POST /api/corestack/sites/{site}/cloudflare/ssl-rules](https://docs.corefinity.com/api/reference/domains/update-site-cloudflare-ssl-rule.md)
- Guide: [Cloudflare for a site](https://docs.corefinity.com/guides/sites/go-live/cloudflare-for-a-site.md)
