Get effective permissions for a user based on roles and teams
AI agents call get_user_permissions to retrieve information from EspoCRM-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves user permission data without modifying, deleting, or executing any operations. It has no side effects and presents minimal risk as it only returns existing permission information. The blast radius is limited to information disclosure of permission metadata, which is low severity in the context of security misuse.
From the tool's definition Tool name 'get_user_permissions' combined with description 'Get effective permissions for a user based on roles and teams' indicates a read operation that retrieves permission information.
Documented attack patterns abuse exactly the kind of access get_user_permissions 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 get_user_permissions:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_permissions": {}
}
}get_user_permissions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get effective permissions for a user based on roles and teams. It is categorised as a Read tool in the EspoCRM-MCP MCP Server, which means it retrieves data without modifying state.
Register the EspoCRM- MCP server in PolicyLayer and add a rule for get_user_permissions: 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.
get_user_permissions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_user_permissions 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 get_user_permissions. 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.
get_user_permissions 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.