by
Grumpy AI Gate Contributors
1 (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 #51,032 among WordPress.org plugins with 1+ active installations, is #3,395 of 4,036 in the Security category, a 1/5 rating from 1 reviews, and was last updated Apr 8, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7
v1.0.1
Current Version v1.0.1
Updated 3 months ago
Last Update on 08 Apr, 2026
Refreshed 8 hours ago
Last Refreshed on
#3,395 of 4,036 in Security
Rank
#51,032
—
No change
Active Installs
1+
—
No change
KW Avg Position
N/A
—
No change
Downloads
333
+1 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(1 reviews)
Next Milestone 10
0+
10+
50,253
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
Need 7 more installs to reach 10+
Rank Changes
Current
#51,032
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
1 reviews
Overall
20%
5
1
(100%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 0 of 0| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| No keyword data available yet. | ||||
Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.0.1
- Last Updated
- Apr 08, 2026
- Requires WP
- 7.0+
- Tested Up To
- 7
- PHP Version
- 7.4 or higher
- Author
- Grumpy AI Gate Contributors
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 1
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
7K+ installs
#2,724
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#992
LiteSpeed Cache
7M+ installs
#5
Akismet Anti-spam: Spam Protection
5M+ installs
#7
Wordfence Security - Firewall, Malware Scan, and Login Security
5M+ installs
#11
Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)
3M+ installs
#17
Hostinger Tools
3M+ installs
#20
WPS Hide Login
2M+ installs
#27
Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention
1M+ installs
#33
WP Super Cache
1M+ installs
#38
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.
