Delete a member
AI agents call buddypress_delete_member to permanently remove resources in BuddyPress MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a member is a destructive action that cannot be undone—it permanently removes user data from the system. This is more severe than Write (which is reversible) and constitutes a destructive operation. In a community management context, unauthorized member deletion could cause significant harm by removing legitimate users and their contributions.
From the tool's definition Tool name contains 'delete' and description states 'Delete a member'. This is an irreversible operation that removes a user account and associated data from a BuddyPress community.
Attacks that exploit this kind of access
Delete a member. It is categorised as a Destructive tool in the BuddyPress MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the BuddyPress MCP Server MCP server in PolicyLayer and add a rule for buddypress_delete_member: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches BuddyPress MCP Server. Nothing to install.
buddypress_delete_member is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the buddypress_delete_member rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for buddypress_delete_member. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
buddypress_delete_member is provided by the BuddyPress MCP Server MCP server (vapvarun/buddypress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →