Grumpy AI Gate: the plugin I built because WordPress AI needed a gatekeeper

Why I built Grumpy AI Gate

I did not set out to build another WordPress plugin.

The idea came out of a problem I ran into while working on the new AI Security Advisor for WP Security Ninja.

As soon as I started building around WordPress 7’s new AI direction, one thing became very obvious to me: there was no good built-in way to see which plugins were actually using AI, how often they were using it, or whether one plugin was quietly chewing through API usage in the background.

That felt like a missing piece.

Because once AI starts spreading across plugins and themes, the question is no longer just “can this site use AI?” The more useful questions become:

• Which plugin is making those requests?
• How often is it happening?
• Which provider is being contacted?
• Roughly how much usage are we talking about?
• Can I stop a specific plugin if I do not want it using AI at all?

I wanted visibility first.

Not another dashboard full of vague promises. Not another service that phones home. Just a straightforward way to see what is happening on a WordPress site when plugins start talking to AI providers.

The original name was painfully boring

At first, I called it AI Usage Monitor.

Which, to be fair, described what it did. It also had all the charm of a cardboard box.

WordPress.org was not too excited about the generic name either, and honestly they were right. So I had to come up with something less lifeless.

That is how it ended up becoming Grumpy AI Gate.

Or GAG, if you like the short version.

It fits better anyway. The plugin is a little suspicious by design. It is supposed to sit there, watch what other code is doing, and be grumpy enough to question it.

What Grumpy AI Gate actually does

Grumpy AI Gate is built to help you stay in control as AI features spread across WordPress plugins, themes, and core.

It observes and classifies outbound AI-related traffic that other code on your site is already initiating. It does not run its own AI dashboard, it does not need a cloud account, and it does not send anything to me or to some third-party analytics service.

Everything is stored locally in your own WordPress database.

That means you can use it to:

• see which plugin is involved in AI-related activity
• review a request log
• get a per-plugin usage overview
• spot patterns before API bills or quotas become a surprise
• optionally block selected plugins from using WordPress AI Client flows

That last part matters more than people think.

Sometimes you do not want every plugin on a site deciding it should talk to OpenAI, Anthropic, Google, or whoever else is fashionable this week. Sometimes you want one plugin to use AI and another plugin to stay in its lane.

That is a reasonable thing to want.

It came directly out of a real product problem

I did not build this from theory.

I built it because while working on AI Security Advisor, I realized that as more plugins start adopting the WordPress AI Client, site owners are going to need basic controls that are currently missing.

If you are the person paying for API usage, managing privacy, or maintaining the site, you should not have to guess which plugin is sending prompts out of your server and how often that is happening.

You should be able to see it.

You should be able to monitor it.

And if needed, you should be able to stop a specific plugin from using that path.

That is the entire philosophy behind Grumpy AI Gate.

Visibility first, blocking where it makes sense

I think it is important to be honest about what the plugin does and does not do.

Grumpy AI Gate is strongest as a visibility tool.

It gives you a clearer picture of which plugins are involved, where traffic is going, and how much activity you are seeing.

It also supports optional blocking for plugins that use the WordPress AI Client flow, which gives you a practical way to say, “No, this plugin does not get to generate AI requests on this site.”

That does not magically turn it into a full outbound AI firewall for every possible HTTP request. I did not want to pretend otherwise.

The point is not to oversell it. The point is to give WordPress site owners and developers something they can actually use today.

Why I think this matters

AI usage on websites is still early enough that a lot of people are not thinking about governance yet.

They are still in the “look what this can do” phase.

That phase does not last long.

Very quickly, the more practical questions start showing up:

• Why are we getting charged more than expected?
• Which plugin is making these calls?
• What data is leaving the site?
• Do we actually want this plugin using AI at all?

That is where I think WordPress needs better tooling.

Not just more AI features, but better oversight of the AI features people are already shipping.

Grumpy AI Gate is my first pass at that problem.

Built to stay local

One thing I felt strongly about from the start: this plugin should not create a new privacy problem while claiming to help with AI oversight.

So it does not phone home. It does not use a cloud dashboard. It does not send your logs somewhere else so you can view them inside a prettier app later.

Everything stays on your own site.

That is not just a technical detail. It is part of the point.

Who it is for

I think Grumpy AI Gate is especially useful for:

• site owners who want to understand which plugins are using AI
• agencies managing multiple WordPress sites
• developers testing WordPress 7 AI integrations
• anyone who does not love the idea of invisible API usage happening in the background

If you are happy to let every plugin talk to every AI provider without oversight, you probably do not need this.

If, on the other hand, you prefer to know what is going on before it becomes a bill, a quota issue, or a privacy discussion, then this plugin will probably make sense immediately.

Why the name ended up being right

In the end, I am glad the original generic name did not survive.

Grumpy AI Gate is a better name because it reflects the mood the plugin is supposed to have.

It is not there to be impressed by AI.

It is there to keep an eye on it.

To ask which plugin is doing what.

To help you notice usage patterns early.

And, when necessary, to get grumpy enough to block a plugin that should not be using AI in the first place.

Try it

If that sounds useful, you can find the plugin here:

https://wordpress.org/plugins/grumpy-ai-gate/

I built it because I needed it while building something else.

That is often a pretty good sign that other people are going to need it too.