---
title: "corestack_site_platform_plugins_set"
url: https://docs.corefinity.com/mcp/tools/corestack_site_platform_plugins_set
type: tool
last_updated: 2026-11-13
feature: platform-plugins
related:
  - https://docs.corefinity.com/api/reference/runtime/update-site-platform-plugins.md
  - https://docs.corefinity.com/guides/sites/software-and-services/platform-plugins.md
---
# corestack_site_platform_plugins_set

**Turn the platform plugins on or off.** Turn Corefinity's platform plugins on or off for a WordPress row (the site's managing agency only). Off, the platform adds none and removes its own; one-click wp-admin login is refused and the preview address, the pre-go-live hold, the PHP mail From address and the preview guard stop. Turning off needs confirm_off: true once the person agreed to what stops (corestack_site_platform_plugins_get lists it, with off_warning on a production row); it is refused once a production site is past its go-live hold. Turning them back on is always allowed. Scope: write. Long-running: answers with a task.

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

## When to use it

Turn Corefinity's platform plugins off, or back on, for one WordPress row (the site or one of its environments). Only the site's managing agency can; the client alone cannot.

Off, the platform adds none of its plugins to the row and removes the files it put there (only files that are byte for byte its own, never a file of the same name the site's owner wrote). From then:

- "Log in to wp-admin" (the function `wp_login_link`) is refused with `platform_plugins_off`;
- the preview address, the pre-go-live hold on email, payments and outgoing requests, the From address for email sent with PHP mail, and the guard on a preview environment stop, while the rest of the site keeps working.

Read `stops` from `corestack_site_platform_plugins_get`, tell the person, and send `confirm_off: true` only once they have agreed. Turning them back on needs no confirmation: the loader is written back at once.

On a production site (`keyed: true` in the read), also tell the person `off_warning` before they agree: turning them off ends the go-live hold on email, outgoing requests, payment gateways and Action Scheduler tasks, up to about a minute after the platform applies the change. Turning them off is refused once the site is past its go-live hold; turning them back on is always allowed, and brings the hold back the same way. While they are off, such a site cannot go live: corestack_site_attach_domain refuses with `platform_plugins_off` until they are back on, then with `platform_plugins_applying` until the task this tool answers has completed.

On a production site the switch changes at once and starts the `platform_plugins_key` operation that applies it, and the answer is that operation's task: poll it with tasks/get, or corestack_task_get if your client has no tasks support. Its `work` names the operation (`kind: operation`, `id`), which corestack_site_operation_get also reads. The task completes once the platform has applied the change, with the result `{operation: {id, site_id, status}}`. It ends with `work_failed` when the platform could not apply it: the setting stays as you chose, but the site cannot go live until the same change, made again, has applied.

When no operation starts the answer comes at once, `{platform_plugins, changed, operation: null}`: on a row that is not a production site, and when there is nothing to do. Asking for the state the row already has changes nothing and answers `changed: false`. The one exception is a production site whose last change of this kind failed (its task ended with `work_failed`, or corestack_site_attach_domain answers `platform_plugins_applying` long after it): asking for the same state again starts a new operation for it and answers its task. When the platform already holds that state, the new operation asks it to apply it again.

## Inputs

- `site_id` (integer, ≥ 1, required): The row: the site or one of its environments.
- `enabled` (boolean, required): true turns the platform plugins on, false turns them off.
- `confirm_off` (boolean): true once the person agreed to what stops; needed to turn them off.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "confirm_off": {
      "description": "true once the person agreed to what stops; needed to turn them off.",
      "type": "boolean"
    },
    "enabled": {
      "type": "boolean"
    },
    "site_id": {
      "description": "The row: the site or one of its environments.",
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "site_id",
    "enabled"
  ],
  "type": "object"
}
```

## Refusals

- `confirm`: a turn-off without `confirm_off: true`; `details.stops` lists what stops. Nothing changed.
- `forbidden`: only the site's managing agency (or Corefinity staff) can change the platform plugins.
- `wrong_platform`: the row is not a WordPress site.
- `runtime_lacks_capability`: the row's runtime cannot turn them off yet; Corefinity support can move it to a newer runtime first.
- `site_cut_over`: a production site past its go-live hold keeps its platform plugins (they send its email from its verified address). Nothing changed; do not try again.
- `cut_over_unknown`: the site could not confirm whether it is past its go-live hold, so nothing was changed. Try again in a minute.
- `busy`, `deployment_running`, `command_running`, `restore_running`: the site is doing something else (a change, a deployment or its rollback, a command, a restore); try again when it finishes.
- `unavailable`: the site refused the change just now, or the platform could not save it; nothing was changed. Try again in a minute.
- `switched_off`: site commands are switched off at the moment; stop and tell the person.
- `managed_elsewhere` (message: "This site is managed by another control panel"): another control panel manages this site, so use that control panel for it. This is refused before anything else about the site, as in the Control Panel and the API. 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).

A task that ends with `work_failed` names the operation in `details.operation`; read its `error` with corestack_site_operation_get, and make the same change again in a minute.

## Example

Turn them back on for a production site; the answer is a task on the operation that applies it.

```json
{
  "name": "corestack_site_platform_plugins_set",
  "arguments": {
    "site_id": 4211,
    "enabled": true
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_site_platform_plugins_set with site_id 4211, enabled true. (Turn the platform plugins on or off.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [PUT /api/corestack/sites/{site}/platform-plugins](https://docs.corefinity.com/api/reference/runtime/update-site-platform-plugins.md)
- Guide: [Platform plugins](https://docs.corefinity.com/guides/sites/software-and-services/platform-plugins.md)
