See which WordPress plugins are using AI — and take back control.
Grumpy AI Gate
As AI features spread across WordPress, site owners need visibility before costs, surprises, and data leakage become a problem. Grumpy AI Gate helps you monitor AI-related activity initiated by other code on your site, shows which plugin is involved, and can optionally block selected WordPress AI Client flows.
- Free plugin on WordPress.org
- No telemetry
- Everything stored locally
- Built for WordPress 7+
Works locally in your WordPress admin - No cloud account required - No third-party analytics - No external AI APIs used by this plugin itself
WordPress is getting AI fast — but control has lagged behind
Plugins can now trigger AI activity for content generation, assistants, SEO features, and other workflows. The problem is that site owners often do not have a clear way to see which plugin is making requests, how often it happens, or whether those requests should be allowed at all. Grumpy AI Gate was built to close that gap.
Whether you are worried about API costs, plugin behavior, privacy, or just visibility, this plugin gives you a practical first layer of control.
What it does
See AI activity before it becomes a surprise
Grumpy AI Gate helps you stay in control as AI features spread across WordPress by observing AI-related outbound traffic that other plugins, themes, or WordPress core already initiate. It gives you a clearer picture of what is happening on your site without adding another cloud dependency. bility
Get dashboard summaries, a per-plugin usage table, and a request log so you can quickly spot which plugin is involved and where activity is coming from. d awareness
AI API usage adds up. Logging helps you spot patterns early so invoices, quota limits, or runaway experiments do not blindside you. r sharing
When you know what leaves your server, it becomes much easier to judge what should and should not be sent in prompts. onal blocking
For WordPress AI Client flows that respect the relevant filter, you can block selected plugins from generating prompts through that path. t works
Built for visibility first, without phoning home
When the WordPress AI Client is available, Grumpy AI Gate records requests from the core lifecycle hooks. For plugins that bypass that route and talk directly to providers, the plugin can also inspect outbound HTTP requests already initiated elsewhere on the site and log recognized AI provider traffic. In the current release, that HTTP fallback is for visibility, not full blocking. t points:
- Grumpy AI Gate does not open AI provider connections for its own purposes
- It filters and classifies traffic initiated elsewhere on the site
- HTTP fallback logging helps even when plugins skip the core AI Client path
- Blocking is currently limited to supported WordPress AI Client flows, not every possible outbound request eople will want it
Why Grumpy AI Gate matters
Most site owners do not mind useful AI features.
What they mind is invisible behavior.
If a plugin starts making paid AI calls in the background, you should be able to see it.
If prompts are leaving your site, you should know which plugin is responsible.
If a plugin should not be using WordPress AI flows, you should have a way to stop it.
That is exactly the hole Grumpy AI Gate is designed to fill.
Your AI monitoring should not create another privacy problem
Grumpy AI Gate is intentionally local-first.
There is no cloud account, no remote analytics, and no telemetry from this plugin. Provider names and URL patterns are only used as local matching rules to classify traffic that other software on your site is already sending. ns you get visibility without handing another service access to your site’s usage data.
Compatibility section
Built for WordPress 7+
Grumpy AI Gate requires WordPress 7.0+ and is designed to work alongside WordPress AI Client functionality where available. It also includes HTTP fallback logging for recognized provider endpoints, which remains important because many plugins may still use direct HTTP calls instead of the AI Client path. Release testing included WordPress 7.0 Beta 5. t limitations section
What the plugin does -not- do
Grumpy AI Gate is a control and visibility plugin, not a full outbound firewall.
- It does not block every possible AI-related HTTP request in the current release
- HTTP fallback is currently for logging and visibility
- Blocking applies to WordPress AI Client flows that respect the relevant prevent hook
- Hard spend limits should still be handled with provider dashboards, quotas, and API key controls easer
Common questions
Does it block all AI traffic?
No. In the current release, blocking applies only to selected WordPress AI Client flows. Direct outbound HTTP calls from plugins can still be logged for visibility, but they are not universally blocked.
Is there any data sent to you?
No. Logs and settings stay on your server, and the plugin does not add off-site tracking or analytics. it still work if WordPress AI Client is not available?
Yes. The plugin loads safely, and HTTP fallback can still log recognized provider traffic initiated by other code on the site. ection
Download Grumpy AI Gate free
Get visibility into AI-related plugin activity on your WordPress site and stop supported AI Client flows where needed.
Written by Lars Koudal
