Two different boundaries

WordPress MCP permissions vs structure control

Giving an agent permission to edit a page does not mean every part of that page should become movable, removable or replaceable.

The distinction Permissions control which operations are available. Structure rules control what those permitted operations may change inside a managed page.

What each layer controls

Permissions and structure solve different problems

Both layers are useful. They answer different questions and should be checked separately.

QuestionPermission controlStructure control
Can this user or agent edit the page at all?Yes. Roles, capabilities and exposed operations can allow or deny the action.No. Structure rules assume an allowed edit has already reached the page.
Can a required section be deleted or moved?Not necessarily. Broad edit permission does not define the allowed internal shape of the page.Yes. Named sections, order and allowed insertion points can be kept under explicit rules.
Can approved content still be changed?Yes, when the operation is permitted.Yes, while protected parts of the page remain fixed.

Use the boundary that matches the risk

Permission control

Use it to limit access to operations

  • Separate read, draft, proposal and publication capabilities.
  • Expose only the operations a role actually needs.
  • Keep application permissions independent from model instructions.

Structure control

Use it to protect the shape of managed pages

  • Keep required sections and their order intact.
  • Allow edits only in declared content areas.
  • Let added blocks remain flexible without opening the protected structure.

Common questions

Where the two controls meet

Is a system prompt enough to protect page structure?

No. Instructions can describe the intended result, but the application must enforce the allowed operations and accepted page structure.

Does structure control replace WordPress roles?

No. Roles and capabilities decide who may perform actions. Structure rules apply an additional boundary inside managed content.

Can an editor still change text and images?

Yes, when those areas are marked as editable. The surrounding section can remain protected.

Where does human review fit?

Review controls whether a prepared change reaches published content. It complements permission and structure checks rather than replacing them.

See the implementation

Follow the checks from request to review

The architecture guide shows where operation permissions, page-structure rules and human approval are enforced in the Agent Composer flow.