Server prompt: change a POM header style

Request change_pom_header_style through prompts/get. It takes no arguments and returns a planning workflow for POM Theme header settings.

The generated instruction tells the client to read pom://theme/header-style-guide, inspect the relevant live setting groups and current values, prepare a batch, dry-run it, and apply only intentional fields. Image assets must be uploaded before their attachment values are used.

Important default limitation

The prompt can discover and propose header changes, but the default MCP POM Theme write allowlist does not include header fields. A dry run can therefore report that a selected field is not writable. That is the expected security boundary, not a reason to use a generic option write.

Use this prompt when you want the client to produce a precise, reviewable header proposal. If the fields are denied, make the final change in the POM Theme settings interface or have a developer deliberately extend the allowlist for the exact supported fields.

Suggested follow-up instruction:

Prepare the header change only. Show the setting group, exact field names,
current values, proposed values, and dry-run result. Do not apply a write or
try another storage path when a field is outside the MCP allowlist.

Verify the proposal on desktop and mobile, including sticky states, navigation access, logo contrast, focus visibility, and generated styles.

Related guides: header resource, POM Theme batch update, and generic theme-mod boundary.