Elimina un webhook del portal Enterprise. OPERACIÓN DE ESCRITURA.
AI agents call webhook_delete to permanently remove resources in ArcGIS MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of webhooks is irreversible and destroys configuration state. While marked as a write operation in the description, the actual function (delete) is destructive. This goes beyond reversible modification into the Destructive category because webhook deletion cannot be easily recovered and may break dependent automation flows.
From the tool's definition Tool name 'webhook_delete' explicitly deletes a webhook. Description states 'Elimina un webhook' (deletes a webhook) and marks it as 'OPERACIÓN DE ESCRITURA' (write operation), but deletion is irreversible.
Attacks that exploit this kind of access
Elimina un webhook del portal Enterprise. OPERACIÓN DE ESCRITURA. It is categorised as a Destructive tool in the ArcGIS MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ArcGIS MCP server in PolicyLayer and add a rule for webhook_delete: 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_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the webhook_delete 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_delete. 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_delete 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 →