Remove a user from an AAP team.
AI agents call aap_remove_user_from_team to permanently remove resources in AAP MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a user from a team revokes their team-based roles, permissions, and access to automation resources. This action is effectively irreversible in the sense that it cannot be automatically undone — it requires deliberate re-addition.
From the tool's definition "Remove a user from an AAP team" — the word 'remove' indicates irreversible disassociation of a user from a team, revoking access and permissions without a recoverable undo operation.
Attacks that exploit this kind of access
Remove a user from an AAP team. It is categorised as a Destructive tool in the AAP MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AAP MCP Server MCP server in PolicyLayer and add a rule for aap_remove_user_from_team: 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 AAP MCP Server. Nothing to install.
aap_remove_user_from_team 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 aap_remove_user_from_team 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 aap_remove_user_from_team. 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.
aap_remove_user_from_team is provided by the AAP MCP Server MCP server (srinivassrinu842/aap-mcp-server). 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 →