AI agents use assign_role_to_user 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 modifies user account properties (role assignment) which is reversible via reassignment. It does not delete data (thus not Destructive), does not move money (not Financial), and does not execute arbitrary code (not Execute). It creates or modifies data reversibly, fitting the Write category.
From the tool's definition Tool name 'assign_role_to_user' and description 'Assign a role to a user' indicate modification of user permissions/attributes in EspoCRM.
Documented attack patterns abuse exactly the kind of access assign_role_to_user 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 assign_role_to_user:
{
"version": "1",
"default": "deny",
"tools": {
"assign_role_to_user": {
"limits": [
{
"counter": "assign_role_to_user_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}assign_role_to_user 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.
Assign a role to a user. 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 assign_role_to_user: 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.
assign_role_to_user 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 assign_role_to_user 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 assign_role_to_user. 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.
assign_role_to_user 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.