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

**Platform plugins.** Whether Corefinity's platform plugins (small must-use plugins that one-click wp-admin login, the preview address and the pre-go-live hold rely on) are on for a WordPress row, the layout detected (standard WordPress or Bedrock), and what stops while they are off. Scope: read.

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

## When to use it

Read whether Corefinity's platform plugins are on for a WordPress row, and which WordPress layout the platform found in the site's files: `classic` (standard WordPress) or `bedrock` (a Roots Bedrock project, where WordPress lives in `web/wp` and the settings in the project's `.env`).

The platform plugins are small must-use plugins Corefinity adds so the Control Panel's tools work: one-click login to wp-admin, the preview address on the platform host, 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. `stops` lists, in the person's words, what stops while they are off; `refused_functions` names the functions refused then (`corestack_function_run` answers `platform_plugins_off` with `reason`).

Read it before `corestack_site_platform_plugins_set`: `can_change` says whether the person may change it (the site's managing agency), and `runtime_ready` whether the row's runtime can turn them off yet.

On a production WordPress site whose runtime keeps the production guard on the platform's own setting (`keyed: true`):

- `cut_over: true` with `off_refused` (a sentence): the site is past its go-live hold, so turning them off is refused. Do not ask the person to confirm; turning them back on is always allowed.
- otherwise `off_note` says turning them off is refused once the site is past its go-live hold (the site gives the final answer when the change is made), and `off_warning` says what stops being held — email, outgoing requests, payment gateways and Action Scheduler tasks — and that it takes effect up to about a minute after the platform applies the change. Tell the person both before they agree.
- `applying: true` while the last change is still being applied by the platform, or while the platform is putting back a change that did not go through. `enabled` is then the setting the site still has, not the one that is coming.
- `needs_attention` (a sentence, else null): the platform could not confirm the setting after the last change, so `enabled` may not be what the site runs, and the site cannot go live. Tell the person the sentence: it names the step they can take. Where it says turning them on (or off) again confirms it, `corestack_site_platform_plugins_set` with that state does, the same state `enabled` already shows included; where it says to contact support to confirm it, this person cannot change it.

Reading never runs anything on the site.

## Inputs

- `site_id` (integer, ≥ 1, required): The row: the site or one of its environments.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "site_id": {
      "description": "The row: the site or one of its environments.",
      "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).

A row that is not WordPress is not refused: it answers `applies: false` and `enabled: true` (there is nothing to turn off).

## Example

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

## Prompt

```text
Using the Corefinity MCP server, call corestack_site_platform_plugins_get with site_id 4211. (Platform plugins.) Tell me what it returned.
```

## The same task elsewhere

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