Desactiva la cuenta de un usuario. OPERACIÓN DE ESCRITURA.
AI agents use user_disable to create or update resources in ArcGIS MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ArcGIS MCP environment.
This tool modifies user state (account enabled → disabled) reversibly. While the impact is significant (user lockout), the action can be undone by re-enabling the account. This qualifies as Write rather than Destructive. Severity is high because disabling a user account can disrupt operations and affect multiple systems, but it is not irreversible like deletion.
From the tool's definition Tool name 'user_disable' and description 'Desactiva la cuenta de un usuario' (Disables a user account) explicitly marked as 'OPERACIÓN DE ESCRITURA' (Write operation). Disables user access but does not delete the account or data.
Attacks that exploit this kind of access
Desactiva la cuenta de un usuario. OPERACIÓN DE ESCRITURA. It is categorised as a Write tool in the ArcGIS MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ArcGIS MCP server in PolicyLayer and add a rule for user_disable: 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 ArcGIS MCP. Nothing to install.
user_disable 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 user_disable 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 user_disable. 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.
user_disable is provided by the ArcGIS MCP server (renemorenow/arcgis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →