BuddyPress

At a glance

BuddyPress registers 8 abilities: 5 that only read, 1 that write, and 2 marked destructive. That split is the practical answer to how much of this module can run unattended. Reads cost nothing and are safe to repeat, so discovery is the part to be generous with; the writes are where review belongs, and the destructive calls stop for an explicit confirmation every single time regardless of which profile is active.

What this module is for

Discover BuddyPress members and groups with privacy-minimized output, then create, edit, or delete groups through confirmation-gated WPPilot Pro abilities.

Before you rely on it: Member responses omit email, private profile fields, messages, and private content. The module does not manage messages, activity, friendships, extended profiles, or member roles; deleting a group permanently removes its group records and requires explicit confirmation.

Typical workflows

• Find community members without returning email or private profile data
• Audit public, private, and hidden groups before a change
• Create or revise a group after confirming its name, status, and scope

The BuddyPress integration page covers the same module from the workflow side, with the capability map and the questions worth asking before a first write.

Availability on your site

The BuddyPress module needs three things at once: WPPilot Free as the MCP foundation, an active Pro licence, and the companion plugin detected on the site. Miss any one and the module does not register, which is deliberate: an ability that appears in the tool list but fails at call time is worse than an ability that was never offered. What the connected agent can actually call is then narrowed twice more: by the safety profile active on the site, and by the WordPress capabilities of the user behind the credential. A read that succeeds for an administrator can be absent entirely for an editor.

Every write these abilities perform is recorded in the change ledger, and destructive calls can be routed through the approval queue so a person signs off before anything is applied. A successful tool result means the operation returned, not that the front end, the cache, and every dependent template are correct: that still needs a look.