MCP boundaries
POM AI publishes a deliberately bounded WordPress administration surface. If an operation is absent from tools/list, the client must not recreate it through post meta, raw options, invented REST routes, or another broad write tool.
Outside the built-in surface
| Area | Boundary |
|---|---|
| Other editors | No Elementor data authoring or generic block-editor conversion. |
| Site administration | No user, credential, plugin, theme, backup, database, filesystem, deployment, DNS, or server management. |
| WordPress configuration | No permalink updates, native Custom CSS writes, generic theme_mod writes, or unrestricted option writes. |
| Content recovery | No revision listing or restore tools. |
| Commerce | Product catalog, variations, and coupons only; no orders or customers. |
| Cache | POM Cache status and clear only; no universal CDN, object-cache, or browser-cache controls. |
| AI service internals | No provider/model inventory through MCP. |
Boundaries are part of the security contract. Tool names, schemas, scopes, WordPress capabilities, write gates, and allowlists work together so a narrow authorization cannot be converted into a broader one.
How to respond
When a task crosses a boundary:
- state which requested outcome is unsupported;
- show the read evidence that led to that conclusion;
- complete any independent supported portion;
- identify the correct WordPress or service interface;
- ask the user to perform or explicitly authorize a separate administrative workflow;
- resume by reading the resulting state, if useful.
Do not claim that dry run, administrator status, or OAuth scope makes a missing operation available.
Related guides: ask for an unsupported operation, MCP authorization, and capability map.
Chapter contents
- Ask for an unsupported operation without guessing
- Elementor content is not a POM MCP authoring format
- Generic theme modifications are not exposed
- Infrastructure and backups require a separate administrative channel
- Cache access is limited to the POM Cache integration
- Native Custom CSS is not writable through MCP
- WooCommerce orders and customers are outside the MCP catalog
- Permalink settings are read-only context
- Plugin and theme administration is not exposed
- MCP does not disclose AI provider or model routing
- WordPress revisions are not an MCP recovery tool
- Users, identities, and credentials are not MCP content