group_update
AI agents use group_update 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.
The tool updates group information reversibly. While the empty description reduces confidence slightly, 'update' operations in administrative contexts typically modify (Write category) rather than delete or execute arbitrary operations. Severity is medium because unauthorized group updates could affect access controls and user permissions across organizations, though impacts are theoretically reversible.
From the tool's definition Tool name 'group_update' indicates modification of group data in ArcGIS. Description is empty, limiting evidence specificity. Context from server description ('group management') confirms this operates on group entities.
Attacks that exploit this kind of access
group_update. 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 group_update: 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.
group_update 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 group_update 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 group_update. 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.
group_update 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 →