POM Theme setting tool reference
Thirteen tools for reading POM Theme's configuration and writing a deliberately narrow part of it.
The tools
Settings
| Tool | Does | Write |
|---|---|---|
pom_theme_get_status |
Is POM Theme usable here? | |
pom_theme_list_settings_schema |
The whole settings structure | |
pom_theme_get_settings_values |
Current values of one setting | |
pom_theme_update_setting |
Change one allowlisted field | Yes |
pom_theme_update_settings_batch |
Change several | Yes |
CSS
| Tool | Does | Write |
|---|---|---|
pom_theme_get_global_css |
Read the global stylesheet | |
pom_theme_update_global_css |
Replace the global stylesheet | Yes |
pom_theme_get_custom_css |
List CSS snippets | |
pom_theme_upsert_custom_css |
Create or update a snippet | Yes |
pom_theme_delete_custom_css |
Delete a snippet | Yes |
Generated assets
| Tool | Does | Write |
|---|---|---|
pom_theme_get_generated_css |
Inspect website.min.css |
|
pom_theme_get_css_build_info |
How that file is built | |
pom_theme_generate_assets |
Rebuild it | Yes |
Almost all of these only exist when POM Theme is active
Among the legacy theme operations, only pom_theme_get_status is always registered. The others appear only when the site passes an availability check — POM Theme active, its constants defined, its framework loaded.
So a client that cannot find pom_theme_get_settings_values is not misconfigured; it is connected to a site not running POM Theme. Ask for the status first, which answers that in one call. See Managing settings for what is available on other themes.
Reading and writing need different capabilities
| Requires | |
|---|---|
| Scopes, reads | mcp:read, pom_theme:read |
| Scopes, writes | mcp:write, pom_theme:write |
| Capability, reads | edit_theme_options |
| Capability, writes | manage_options |
| Write gate | Allow POM Theme writes |
This split is unusual and worth planning around: an editor with edit_theme_options can read the whole theme configuration and change none of it. Writes are administrator-level.
Typed editing and legacy scalar editing
The typed settings workflow discovers editable colours, fonts, header, footer and optional features from native definitions. It requires an explicit preview revision and reports a write policy for every field.
pom_theme_update_setting and pom_theme_update_settings_batch retain their existing scalar allowlist: post and custom-post-type archive/single layout settings. Use the typed patch operation for other supported design fields and dedicated tools for templates, queries and filters.
What is refused outright
| Error | Meaning |
|---|---|
pom_ai_mcp_theme_field_denied |
The field is not on the allowlist |
pom_ai_mcp_js_write_denied |
JavaScript settings can never be written |
pom_ai_mcp_complex_setting_denied |
Arrays and objects need a dedicated tool |
pom_ai_mcp_css_denied |
The CSS contained PHP tags or </style> |
pom_ai_mcp_template_php_denied |
The HTML contained PHP tags |
pom_ai_mcp_theme_setting_not_found |
No such setting |
Creating or modifying JavaScript source is refused. Agents can assign scripts already in the theme catalog to content and templates.
Writes rebuild the site's stylesheet
Every CSS write regenerates website.min.css automatically, and each returns the resulting asset metadata. That regeneration is what makes the change visible; it is also why a CSS write is heavier than it looks.
You will still need to purge caches afterwards. See Clearing the cache after a change.