WordPress revisions are not an MCP recovery tool

POM AI can read and update posts and pages, but it does not list revisions, compare revision snapshots, or restore a revision.

WordPress may create native revisions when content is updated, depending on site configuration and content type. That background behavior is not a guarantee from the MCP response, and a client must not promise that every write can be undone through MCP.

Prepare recovery before a write

For an important content edit:

• read and retain the current object in the task context;
• show a bounded before/after comparison;
• use a dry run;
• preserve status, slug, parent, template, and unrelated content;
• verify the object after the write.

If rollback is needed, use the WordPress editor’s Revisions interface where available. A WordPress administrator may also restore from a verified backup. POM AI cannot perform either action through its built-in tools.

Deletes require even more care: attachment deletion may be permanent, menu item deletion is permanent in the integration, product deletion is not exposed, and recovery rules vary by object.

Related guides: edit existing page, failed-write recovery, and backups boundary.