webmap_update_layer
AI agents use webmap_update_layer 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 name strongly suggests it updates/modifies layer properties or data within a web map. Without an explicit description, this is inferred from context: ArcGIS servers manage geospatial data, and 'update' indicates a reversible write operation rather than retrieval (Read) or irreversible deletion (Destructive).
From the tool's definition Tool name 'webmap_update_layer' indicates modification of web map layer data or configuration; sibling tools include item management and feature layer editing operations, suggesting this server manages geospatial data with write capabilities.
Attacks that exploit this kind of access
webmap_update_layer. 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 webmap_update_layer: 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.
webmap_update_layer 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 webmap_update_layer 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 webmap_update_layer. 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.
webmap_update_layer 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 →