Grumpy AI Gate
by Lars Koudal 5 (1 reviews)

Grumpy AI Gate

Intercept and log AI-related HTTP from plugins/themes; optional AI Client blocking. All data stays on your server.

Grumpy AI Gate ranks #64,630 among WordPress.org plugins with 0+ active installations, is #3,514 of 4,596 in the Security category, a 5/5 rating from 1 reviews, and was last updated Apr 29, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7.0.6 (Current: 7.1.2)
v1.0.2 Current Version v1.0.2
Updated 4 months ago Last Update on 29 Apr, 2026
Refreshed 9 hours ago Last Refreshed on
#3,514 of 4,596 in Security
View on WordPress.org
Rank
#64,630
No change
Active Installs
0+
-100%
KW Avg Position
N/A
No change
Downloads
422
+1 today
Support Resolved
0%
No change
Rating
100%
Review 5 out of 5
5 (1 reviews)

Next Milestone 10

Total Progress 0%
0+ 10+
44,890
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 10 more installs to reach 10+

Rank Changes

52,977 57,188 61,400 65,611 69,822 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026 23-09-2026
49,951 55,017 60,084 65,150 70,216 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026 23-09-2026
Current #64,630
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026 23-09-2026
0 10 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026 23-09-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

5.0
1 reviews
Overall 100%
5
1 (100%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about Grumpy AI Gate

Plugins can trigger AI calls in the background—for content, assistants, SEO tools, and more. Logging gives you a clear picture of which plugin is active, how often requests run, and where traffic is going, so you can manage budgets and content thoughtfully.
It helps you see usage and trends. Optional blocking reduces some WordPress AI Client traffic for plugins you choose. Outbound HTTP calls to provider APIs that other code makes are logged for visibility in the current release but are not blocked here—use provider dashboards, API keys, and quotas for hard spend limits.
No. Logs and settings stay on your server in the WordPress database. This plugin does not add off-site tracking or analytics.
Blocking applies to WordPress AI Client flows that respect the wp_ai_client_prevent_prompt filter. You choose plugins under Grumpy AI Gate → Settings and save. It is not a full firewall for every outbound request.
No. Only AI Client traffic for plugins you select under Grumpy AI Gate → Settings is blocked (after you save). HTTP calls to provider APIs that other plugins or themes initiate are observed and logged in the current release but not blocked.
Yes. The plugin loads safely. Without the AI Client stack, HTTP fallback can still record calls to recognized provider endpoints when that option is enabled in Settings, as long as other code on the site is making those outbound requests.
When the WordPress AI Client stack is available, a full generation is one log row from its lifecycle hooks; the matching raw provider HTTP for that same call is skipped so usage is not double-counted. Calls that do not fire those hooks (for example listing models) are still logged and may appear with capability provider_http. When another plugin talks to a known AI API without going through core AiClient, or when AI Client monitoring is off in settings, those requests are recorded via HTTP fallback instead.
Only built-in provider host/path rules (OpenAI, Anthropic, Google AI / Gemini, xAI, DeepSeek, Mistral, OpenRouter, and local Ollama). See Grumpy AI Gate → Settings for the current hostname list. Those patterns exist only to filter and classify outbound traffic initiated by other code—they are not endpoints this plugin contacts for its own operation.
Blocking uses WordPress’s wp_ai_client_prevent_prompt filter: it stops prompt builder flows (support checks and generations) that go through that path. Separate calls such as listing models (/v1/models) may still run as provider HTTP on the AI Client channel and appear as a successful row—that traffic does not go through the same prevent hook.
Yes. Under Grumpy AI Gate → Settings, use the options to clear the request log only, or clear the log and aggregated statistics, as needed.

More plugins by Lars Koudal

Sign In / Register

You need to sign in or register to use this feature.