Critical Risk →

remove_team_member

Remove a team member from a project (soft delete)

Part of the Agent Team server.

remove_team_member can permanently delete data in Agent Team, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE AGENT TEAM →

Free to start. No card required.

AI agents may call remove_team_member to permanently remove or destroy resources in Agent Team. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call remove_team_member in a loop, permanently destroying resources in Agent Team. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_team_member"
  ]
}

See the full Agent Team policy for all 46 tools.

Get this rule live on your own Agent Team server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY AGENT TEAM →

View all 46 tools →

These attack patterns abuse exactly the kind of access remove_team_member gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so remove_team_member only ever does what you allow.

SECURE AGENT TEAM →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the remove_team_member tool do? +

Remove a team member from a project (soft delete). It is categorised as a Destructive tool in the Agent Team 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 remove_team_member? +

Register the Agent Team 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 Agent Team. Nothing to install.

What risk level is remove_team_member? +

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.

Can I rate-limit remove_team_member? +

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.

How do I block remove_team_member completely? +

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.

What MCP server provides remove_team_member? +

remove_team_member is provided by the Agent Team MCP server (agent-team-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Agent Team tool call.

Deterministic rules across all 46 Agent Team tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.