MCP authorization
Authentication identifies the client and actor. Authorization is evaluated again for every resource, prompt, and tool call.
Four checks for a write
- OAuth scope: the token must include every scope declared by the tool.
- WordPress capability: the mapped user must be allowed to act on the specific object or product area.
- Write gate: the administrator must have opened the relevant content, option, POM Theme, or WooCommerce gate.
- Schema and allowlist: required arguments, value constraints, post types, meta keys, options, and settings must be accepted.
Typical scope families are:
| Area | Read | Write |
|---|---|---|
| MCP base | mcp:read |
mcp:write |
| WordPress content | wp:content:read |
wp:content:write |
| POM Theme | pom_theme:read |
pom_theme:write |
| WooCommerce catalog | woocommerce:catalog:read |
woocommerce:catalog:write |
Tools also enforce capabilities such as edit_posts, upload_files, moderate_comments, manage_categories, edit_theme_options, manage_options, or WooCommerce management access.
Passing one layer never bypasses another. An administrator without the OAuth write scope is denied; a broad token mapped to a low-privilege user is also denied. Dry run uses the same controls.
Human approval
Applying a write also requires human approval. An exact review authorizes only its listed inputs, once per operation. Network reviews open on the main site for the super administrator who authorized the connection.
For ongoing network editing, route pom_site_request_work_session through pom_network_execute_site with the destination's site_id, a title, the requested write groups and a duration of 1, 4 or 8 hours. The signed-in user must explicitly approve the session on the main site. Subsequent permitted writes supply work_session_id and a new UUID operation_id instead of approval_id. Keep any required expected_revision current. All four authorization checks above still apply on each execution.
A session is restricted to its destination, connection, user and approved tools, with a maximum of 500 operations. It does not authorize deletion tools or composite plans. Revocation, expiry or a changed network policy stops later operations; an uncertain operation pauses the session. Inspect pom_site_get_work_session and the task result before continuing. See confirm writes for the complete workflow.
On independent site connections, POM Cache clear follows its integration capability and does not use a general write gate. Network delegation also requires the cache_writes group.
Related guides: capability map, write denied, and security.