webhook_create
AI agents use webhook_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 a webhook establishes an integration that sends data to an external URL on events, which is a Write operation (reversible, can be deleted). However, it could enable data exfiltration or trigger external systems. Without a description, confidence is reduced. Severity is high because a malicious webhook could forward sensitive GIS data to an attacker-controlled endpoint.
From the tool's definition Tool name 'webhook_create' suggests creating a webhook; description is empty and uninformative.
Attacks that exploit this kind of access
webhook_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 webhook_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.
webhook_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 webhook_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 webhook_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.
webhook_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.
webhook_create is one line of ArcGIS's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →