Can I manage rules with WP-CLI?

Yes. With WP-CLI available and this plugin active: wp aicac rule list — table of every installed plugin (active and inactive) with family-level allow/deny/inherit state. Use `--format=json` for machine-readable output. wp aicac rule set — set one capability-family cell (text, image, speech, tts, video). Writes through the same sanitized policy path as the Rules tab. Plugin basename must match an installed plugin file (e.g. `acme-plugin/acme-plugin.php`), including inactive plugins.

by Haktan Suren 0 (0 reviews)

HandL AI Connector Access Control

Name: HandL AI Connector Access Control
Author: Haktan Suren

See which WordPress plugins use AI. Control access. Track estimated spend before it becomes a surprise.

HandL AI Connector Access Control ranks #62,684 among WordPress.org plugins with 0+ active installations, is #3,855 of 5,058 in the Security category, and was last updated Sep 17, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7.0.8 (Current: 7.1.4)

v1.7.0 Current Version v1.7.0

Updated 1 month ago Last Update on 17 Sep, 2026

Refreshed 1 week ago Last Refreshed on

#3,855 of 5,058 in Security Downloads -7.1% this week

View on WordPress.org

Rank

#62,684

— No change

Active Installs

-100%

KW Avg Position

20.5

— No change

Downloads

1.6K

+5 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 20%

0+ 10+

35,116

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 8 more installs to reach 10+

Rank Changes

Current #62,684

Change

Best #

Upgrade to Pro

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

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

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

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.7.0
Last Updated: Sep 17, 2026
Requires WP: 7.0+
Tested Up To: 7.0.8
PHP Version: 7.4 or higher
Author: Haktan Suren

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

AI ai client governance handl security

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Akismet Anti-spam: Spam Protection

5M+ installs

Wordfence Security – Firewall, Malware Scan, and Login Security

5M+ installs

#11

Really Simple Security – Simple and Performant Security (formerly Really Simple SSL)

Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention

View all Security-and-spam-protection plugins

Frequently Asked Questions

Common questions about HandL AI Connector Access Control

Connector Approvals in the WordPress AI plugin controls which plugins and themes can use configured AI connector credentials. HandL AI Connector Access Control governs AI Client prompts through wp_ai_client_prevent_prompt, adding per-plugin allow/deny rules, a capability-family matrix, tool-arming denial, shadow-AI detection for direct connections outside the AI Client, and estimated spend / denial alerting. Both can run together because they govern different layers. See Dashboard → “Beyond Connector Approvals”.

Only AI calls made through the WordPress AI Client APIs that pass through wp_ai_client_prevent_prompt. The shadow-AI detector can observe direct HTTP to known AI hosts (when logging or Learn mode is on) and, if you enable Block direct calls to known AI providers, can block those requests with optional per-plugin exceptions. AI Client traffic is never treated as shadow traffic.

A plugin (or other PHP code) issued a WordPress HTTP request to a known AI provider host without going through the AI Client path this plugin gates. With blocking off, those rows are labeled observe. With Block direct calls to known AI providers on, they may be denied or allowed as an exception. Plugin Allow/Deny rules still apply only to AI Client traffic.

No. It is best-effort and may be unknown or ambiguous for some execution paths (cron, REST bootstraps, shared libraries, MU plugins). Experimental model force uses the same attribution: a pin follows the detected caller, not a guarantee of which product “owns” the spend.

No. It pins the route for calls we attribute to that plugin’s nearest stack frame. Unattributed calls are unforced by default (configurable). Misattribution can apply another plugin’s pin without failing closed — existence of a resolved plugin is not proof it is the right one.

Yes. With WP-CLI available and this plugin active: wp aicac rule list — table of every installed plugin (active and inactive) with family-level allow/deny/inherit state. Use `--format=json` for machine-readable output. wp aicac rule set <plugin-basename> <family> <allow|deny|inherit> — set one capability-family cell (text, image, speech, tts, video). Writes through the same sanitized policy path as the Rules tab. Plugin basename must match an installed plugin file (e.g. `acme-plugin/acme-plugin.php`), including inactive plugins.