Cache access is limited to the POM Cache integration
When POM Cache is available, POM AI can read its status and request a cache clear. That is the complete built-in cache surface.
It does not expose:
- arbitrary path or URL purges;
- cache warming;
- POM Cache configuration changes;
- WordPress object-cache flushing as a public MCP tool;
- host-level page cache;
- CDN invalidation;
- reverse-proxy control;
- browser cache clearing.
Interpret a clear correctly
A successful pom_cache_clear_site_cache response confirms the action handled by the connected POM Cache integration. It does not prove that every external layer has expired. Always verify the underlying post, option, or template first, then check the public URL in the relevant environment.
If POM Cache tools are missing, refresh tools/list and inspect integration status. Do not use another write tool to simulate a purge. If the visible stale page is controlled by a CDN or host cache, hand the exact URL and timestamp to that system’s administrator.
Cache clear is a state-changing operation even though it does not modify editorial content. Obtain confirmation when it affects a production site, and avoid repeated clears while diagnosing a wrong saved value.
Related guides: POM Cache tools, clear-cache recipe, and MCP tool missing.