Remove participantes de um grupo na Zappaz API
AI agents call remove_participants to permanently remove resources in Zappaz MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing participants from a group is an irreversible action (the members are kicked out and lose access to the group). This cannot be undone automatically — re-adding them requires a separate action and their consent. The blast radius is high as it could remove multiple members from important group communications.
From the tool's definition Remove participantes de um grupo na Zappaz API — 'Remove participantes' indicates irreversible removal of participants from a group
Attacks that exploit this kind of access
Remove participantes de um grupo na Zappaz API. It is categorised as a Destructive tool in the Zappaz MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Zappaz MCP Server MCP server in PolicyLayer and add a rule for remove_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 Zappaz MCP Server. Nothing to install.
remove_participants 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 remove_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.
Set action: deny in the PolicyLayer policy for remove_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.
remove_participants is provided by the Zappaz MCP Server MCP server (viiniolliveira/zappaz-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 →