POM Cache tool reference
Two tools: read the cache's state, and clear it.
| Tool | Does | Write |
|---|---|---|
pom_cache_get_status |
Availability and statistics | |
pom_cache_clear_site_cache |
Delete the cached output | Yes |
Permissions
| Requires | |
|---|---|
| Scope, read | mcp:read |
| Scope, write | mcp:write |
| Capability | manage_options for both |
Two things differ from every other chapter.
There is no write gate. The four gates in POM AI MCP settings cover content, options, POM Theme and WooCommerce. Cache clearing is behind none of them: a client with mcp:write and an administrator identity can purge the cache with no gate to open first.
That is defensible — clearing a cache destroys generated files, not data, and everything it removes is rebuilt on the next page load. But it means "all write gates are closed" does not mean "nothing can be written". If that is not acceptable on a given site, the control is the OAuth scope, not a gate.
Both tools are always registered, whether or not POM Cache is installed. pom_cache_get_status reports availability; the clear tool returns pom_ai_mcp_pom_cache_unavailable if the plugin is absent.
So unlike the POM Theme tools, a missing POM Cache does not make these tools disappear. Their presence is no evidence the plugin is installed.
Two caches
POM Cache stores two things, and the tools treat them separately:
| Contains | Cleared | |
|---|---|---|
| HTML cache | Rendered pages | Always |
| Progressive JSON cache | Data for progressive loading | Only if supported, and only when asked |
A site can support the HTML cache without the JSON one. The status tool reports each independently.
What these tools do not cover
Only this site's POM Cache. On a multisite network, one site — there is no network-wide purge, and each site needs its own call from its own connection.
And only POM Cache. Object caches, opcode caches, hosting-level page caches, CDNs and browser caches are all untouched. On most production sites a POM Cache purge is one step of several, and the CDN is usually the one that makes a change visible.
See Limited cache access for what is genuinely out of reach.
When it matters
Almost every write in POM AI produces a change that a cache will hide. The pattern is the same throughout the documentation:
- Make the change.
- Verify the stored data.
- Clear the cache.
- Clear the CDN.
- Look at the site.
Skipping step 3 is the most common reason a correct write appears not to have worked.
See Clearing the cache after a change.
Related
- Theme setting tools — writes that need a purge afterwards
- Limited cache access
- The capability map — gates, scopes and capabilities together