Remove a team member by ID.
AI agents call remove_team_member to permanently remove resources in Payoza MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a team member permanently revokes their access to the platform. This is an irreversible destructive action (the member must be re-added manually), with high blast radius since an AI agent misusing this tool could inadvertently remove legitimate team members, disrupting operations and access control.
From the tool's definition 'Remove a team member by ID' — removal of a team member is an irreversible organizational action that revokes access and cannot be undone without re-invitation.
Attacks that exploit this kind of access
Remove a team member by ID. It is categorised as a Destructive tool in the Payoza MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Payoza MCP Server MCP server in PolicyLayer and add a rule for remove_team_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 Payoza MCP Server. Nothing to install.
remove_team_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 remove_team_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 remove_team_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.
remove_team_member is provided by the Payoza MCP Server MCP server (payoza/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 →