webmap_create
AI agents use webmap_create 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.
Creating webmaps is a reversible data modification operation—new webmaps can be deleted or modified afterward. This is a Write-category action. Severity is medium because creating unauthorized webmaps could clutter the system, share sensitive geographic data, or be used for social engineering, but the impact is limited without accompanying permissions to publish widely or access restricted content.
From the tool's definition Tool name 'webmap_create' directly indicates creation of a new webmap resource in ArcGIS; the pattern aligns with other write operations on this server (item management capability mentioned in server description).
Attacks that exploit this kind of access
webmap_create. 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_create: 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_create 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_create 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_create. 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_create 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 →