---
title: Grumpy AI Gate
canonical: https://wpsecurityninja.com/gaig/
---
# See which plugins are using AI. Then decide what stays allowed.

Monitor AI-related activity on your WordPress site, spot which plugin is involved, and optionally block selected WordPress AI Client flows. Free, local, no cloud account.

- [Download free](https://wordpress.org/plugins/grumpy-ai-gate/)
- [Watch the walkthrough](#video)
- [Why I built it](https://wpsecurityninja.com/grumpy-ai-gate/)

## Highlights

- Free on WordPress.org
- No cloud account
- Everything stored locally
- Built for WordPress 7+

## Control before AI surprises become a problem

### Visibility

Dashboard summaries, a per-plugin usage table, and a request log so you can see which plugin is involved and where activity is coming from.

### Spend awareness

AI API usage adds up. Logging helps you spot patterns early so invoices, quota limits, or runaway experiments do not blindside you.

### Safer sharing

When you know what leaves your server, it is much easier to judge what should and should not be sent in prompts.

### Optional blocking

For WordPress AI Client flows that respect the prevent hook, you can block selected plugins from generating prompts through that path.

## WordPress is getting AI fast. Control has lagged behind.

Plugins can now trigger AI activity without a clear way to see who made the request, how often it happens, or whether it should be allowed. Grumpy AI Gate closes that gap.

- See AI-related activity initiated by other code on your site
- Identify which plugin is involved
- Spot patterns before costs or data leakage become a surprise

## How it works

When the WordPress AI Client is available, Grumpy AI Gate records requests from core lifecycle hooks. For plugins that talk to providers over HTTP instead, it can inspect outbound requests already in flight and log recognized AI provider traffic.

- Does not open AI provider connections for its own purposes
- Filters and classifies traffic initiated elsewhere on the site
- HTTP fallback is for visibility in the current release, not full blocking
- Blocking applies to supported WordPress AI Client flows

## What the plugin does not do

Grumpy AI Gate is a control and visibility plugin, not a full outbound firewall. Hard spend limits still belong in provider dashboards, quotas, and API key controls.

- Does not block every possible AI-related HTTP request today
- HTTP fallback currently logs and classifies, it does not stop those calls
- Blocking needs WordPress AI Client flows that respect the prevent hook

## Your AI monitoring should not create another privacy problem

Everything stays on your server. There is no cloud account, no remote analytics, and no telemetry from this plugin. Provider names and URL patterns are local matching rules only.

- Logs and settings stay in your WordPress database
- No third-party analytics from this plugin
- You get visibility without handing another service your usage data

## FAQ

### 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 any data sent to you?

No. Logs and settings stay on your server. The plugin does not add off-site tracking or analytics.

### Does 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.

### What WordPress version do I need?

Grumpy AI Gate requires WordPress 7.0+. Release testing included WordPress 7.0 Beta 5.

## Download Grumpy AI Gate free

Get visibility into AI-related plugin activity on your WordPress site, and stop supported AI Client flows where needed.

[Download free](https://wordpress.org/plugins/grumpy-ai-gate/)