Quita un item de un grupo via SharingGroupManager. OPERACIÓN DE ESCRITURA.
AI agents use share_group_remove 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.
Removing an item from a group modifies the sharing/membership relationship but does not permanently delete the item or the group itself. The action is reversible (the item can be re-added), placing it in the Write category rather than Destructive. Misuse could revoke access for group members to shared content, giving it medium severity.
From the tool's definition 'Quita un item de un grupo via SharingGroupManager. OPERACIÓN DE ESCRITURA.' — removes an item from a group, explicitly labeled as a write operation
Attacks that exploit this kind of access
Quita un item de un grupo via SharingGroupManager. 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 share_group_remove: 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.
share_group_remove 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 share_group_remove 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 share_group_remove. 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.
share_group_remove 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 →