New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

growsurf_bulk_delete_participants

Bulk delete participants from your GrowSurf program in one request. DESTRUCTIVE: deletion is permanent, cannot be undone, and removes the participants

SERVERGrowSurf SOURCE@growsurfteam/growsurf-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-growsurf-growsurf/growsurf-bulk-delete-participants.md

What growsurf_bulk_delete_participants does on GrowSurf

AI agents call growsurf_bulk_delete_participants to permanently remove resources in GrowSurf, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why growsurf_bulk_delete_participants is rated Critical

An AI agent that decides to call growsurf_bulk_delete_participants doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from GrowSurf is gone. There is no undo for destructive operations.

Questions about growsurf_bulk_delete_participants

What does the growsurf_bulk_delete_participants tool do? +

Bulk delete participants from your GrowSurf program in one request. DESTRUCTIVE: deletion is permanent, cannot be undone, and removes the participants. It is categorised as a Destructive tool in the GrowSurf MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on growsurf_bulk_delete_participants? +

Register the GrowSurf MCP server in PolicyLayer and add a rule for growsurf_bulk_delete_participants: 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 GrowSurf. Nothing to install.

What risk level is growsurf_bulk_delete_participants? +

growsurf_bulk_delete_participants is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit growsurf_bulk_delete_participants? +

Yes. Add a rate_limit block to the growsurf_bulk_delete_participants 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.

How do I block growsurf_bulk_delete_participants completely? +

Set action: deny in the PolicyLayer policy for growsurf_bulk_delete_participants. 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.

What MCP server provides growsurf_bulk_delete_participants? +

growsurf_bulk_delete_participants is provided by the GrowSurf MCP server (@growsurfteam/growsurf-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on GrowSurf, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GrowSurf's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.