AI agents use add_user_to_team to create or update resources in EspoCRM-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EspoCRM-MCP environment.
This tool creates a new team membership relationship and modifies organizational structure data. It is reversible (the user can be removed from the team), so it falls under Write rather than Destructive. The medium severity reflects that inappropriate team assignments could grant unintended access or visibility, but the effect is limited in scope and can be undone.
From the tool's definition Tool description states 'Add a user to a team' - this is a create/modify operation that adds a user membership to a team, a reversible action. The optional 'position' parameter further indicates data modification.
Documented attack patterns abuse exactly the kind of access add_user_to_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 add_user_to_team:
{
"version": "1",
"default": "deny",
"tools": {
"add_user_to_team": {
"limits": [
{
"counter": "add_user_to_team_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_user_to_team stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a user to a team with optional position. It is categorised as a Write tool in the EspoCRM-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the EspoCRM- MCP server in PolicyLayer and add a rule for add_user_to_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.
add_user_to_team is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_user_to_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 add_user_to_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.
add_user_to_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.