SpeedyCache
ConditionalOnce enabled, an agent can read the site's caching, file optimization, and CDN configuration, check cache and preload status, and clear or rebuild the cache.
7 read5 destructive
View abilitiesPrevent Browser Caching abilities, governed through the Bridge
An agent can force every visitor's browser to fetch fresh CSS, JS, and images after a site change, optionally purging the page cache too, and can read back the plugin's current cache-busting configuration and status.
- Abilities
- 21 read1 write
- Active installs
- 10K+
- Rating
- 98% (29 ratings)
- Version
- 3.2.1
- Requires
- WP 4.7+, PHP 7.2+
- Last updated
- 2026-08-21
View Prevent Browser Caching on WordPress.org
What has to be true first
Needs WordPress 6.9 or later with Prevent Browser Caching active. Both abilities check the manage_options capability, so only a WordPress administrator can use them through the Bridge.
A note on the count below
Both abilities read directly from the plugin's single ability-registration file, matching the directory's count of 2 exactly.
The 2 Prevent Browser Caching abilities
Grouped by what each one can change. Every one starts off until you enable it.
Read 1
- Read
Get cache-busting status
Reports the site's current versioning mode, what is versioned, and the detected page cache plugin.
Write 1
- Write
Update asset versions
Makes browsers fetch current CSS, JS, and images instead of cached copies, and optionally purges the page cache.
How to switch these on
Four steps from two active plugins to a governed connection.
Install Prevent Browser Caching and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. Prevent Browser Caching registers its own abilities; this plugin discovers and governs them.
Open the Other plugins screen
In Agent Abilities for MCP, open the Bridge tab (labeled "Other plugins" in the admin). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Enable one ability at a time
Every ability from Prevent Browser Caching starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Connect as a least-privilege user
Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.
Read more in how bridging works or the full documentation.
Frequently asked questions
Does Prevent Browser Caching work with the Bridge?
Yes. The plugin registers its two operations as core WordPress abilities with no extra setting, so the Bridge can list and wrap both once the operator switches them on.
Do Prevent Browser Caching's abilities register automatically?
Yes, unconditionally, once Prevent Browser Caching is active. Nothing else has to be configured for the Bridge to discover them.
Does Prevent Browser Caching need anything special to work with the Bridge?
Needs WordPress 6.9 or later with Prevent Browser Caching active. Both abilities check the manage_options capability, so only a WordPress administrator can use them through the Bridge.
More Performance plugins
Jetpack Boost
ConditionalAn agent can list and filter Boost's performance modules, toggle a single module on or off, read the latest mobile and desktop speed score, and clear the page cache.
2 read2 write
View abilitiesAn AI agent can count how many post revisions a site stores and estimate their size, list them a page at a time, delete a bounded batch of revisions for a given scope, and run OPTIMIZE TABLE on the posts and postmeta tables afterward.
2 read2 destructive
View abilitiesVerified from Prevent Browser Caching's own free wordpress.org code on 28 September 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, Kostya Tereshchuk or Prevent Browser Caching. Back to the full directory.
Bridge Prevent Browser Caching, keep the same control.
Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.
Off by default. Capability checked on every call.