AI agents call remove_user_from_team to permanently remove resources in EspoCRM-MCP — 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 is an irreversible access-control change (without a corresponding re-add operation visible in context). It revokes the user's team membership, which can affect their permissions, data visibility, and collaboration access within EspoCRM. This is a destructive action with potentially high blast radius if misused by an AI agent.
From the tool's definition 'Remove a user from a team' — the action explicitly removes/deletes a membership relationship between a user and a team
Documented attack patterns abuse exactly the kind of access remove_user_from_team gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and EspoCRM-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_user_from_team:
{
"version": "1",
"default": "deny",
"hide": [
"remove_user_from_team"
]
}remove_user_from_team disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a user from a team. It is categorised as a Destructive tool in the EspoCRM-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the EspoCRM- MCP server in PolicyLayer and add a rule for 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 EspoCRM-MCP. Nothing to install.
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 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 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.
remove_user_from_team is provided by the EspoCRM- MCP server (zaphod-black/espomcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 46 EspoCRM-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
46 EspoCRM-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.