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

**PHP settings.** A row's three PHP settings (memory limit, upload size, execution time) with the bounds its platform and tier allow, and `version`, which corestack_php_settings_update needs. Scope: read.

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

## When to use it

A row's three PHP settings (memory limit, upload size, execution time) with the bounds its platform and tier allow, and `version`, which corestack_php_settings_update needs.

`notes` (`[{code, text}]`, `[]` when nothing): on an environment whose create changed a setting it carried over to fit the environment's limits, `php_settings_clamped` names each such value while it still applies.

Where the person's Control Panel offers it, the answer also carries `app_cache_header` `{enabled, applies, runtime_ready}`: whether the platform reports the application's own page cache for this row (`enabled`; `false` = the row opted out), whether that means anything here (`applies`: WordPress rows only) and whether the row's runtime already acts on it (`runtime_ready`; `false`: a change is kept and takes effect when the row's runtime is updated). Change it with corestack_php_settings_update's `app_cache_header`.

## 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

- `removed`: the row has been removed.
- `deleted`: the site is deleted (in its grace period); restore it with corestack_site_restore_deleted first.
- `provisioning`: the site is still being created; wait for corestack_site_provisioning_get to finish.
- `not_available`: this row's PHP settings cannot be shown here (a custom tier, or a row the Control Panel does not manage these settings for).
- 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_php_settings_get",
  "arguments": {
    "site_id": 4211
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_php_settings_get with site_id 4211. (PHP settings.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [GET /api/corestack/sites/{site}/php-settings](https://docs.corefinity.com/api/reference/runtime/get-php-settings.md)
- Guide: [PHP configuration](https://docs.corefinity.com/guides/sites/software-and-services/php-settings-and-php-ini.md)
