List pending signups/registrations
AI agents call buddypress_list_signups to retrieve information from BuddyPress MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays pending signup/registration data. It performs a read-only query operation with no capability to modify, delete, or execute actions. The blast radius of misuse is minimal — an AI agent can only view pending registrations, which represents low sensitivity information in a community management context.
From the tool's definition Tool name contains 'list' and description states 'List pending signups/registrations' — a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
List pending signups/registrations. It is categorised as a Read tool in the BuddyPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BuddyPress MCP Server MCP server in PolicyLayer and add a rule for buddypress_list_signups: 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_list_signups is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the buddypress_list_signups 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_list_signups. 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_list_signups 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 →