Generic theme modifications are not exposed

POM AI does not publish a tool for arbitrary WordPress theme_mod values. POM Theme configuration uses its dedicated live schema, read tools, write allowlist, and write gate.

This distinction prevents a client from writing an unvalidated key, bypassing field dependencies, or placing data in a storage path the active theme no longer reads.

Supported POM Theme path

For a POM Theme setting:

1. Call pom_theme_get_settings_catalog.
2. Read the selected group with pom_theme_get_setting_contract.
3. Check each field's writable policy and schema.
4. Preview pom_theme_patch_settings with the intended values.
5. Review the changes and apply with the preview's expected_revision under the site owner's authorization.

The typed contract supports eligible native fields and repeaters while keeping credentials, execution fields and fields requiring dedicated operations outside generic patches. The earlier pom_theme_update_setting tool retains its smaller allowlist for scalar layout and template assignments. Administrator capability does not make a refused field writable.

For another theme, POM AI has no generic settings bridge. Use that theme’s supported administration interface.

wp_update_option is not a fallback: it can write only its separate option allowlist (blogname, blogdescription, posts_per_page, date_format, and time_format). Theme mods and arbitrary theme options are outside it.

Related guides: theme settings pointer, update a theme setting, and native Custom CSS boundary.