fl_delete_fields
AI agents call fl_delete_fields 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.
Deleting fields from a feature layer is an irreversible destructive action that alters the underlying data schema. Even if only metadata is affected, field deletion removes data structure permanently and cannot be recovered without administrative intervention or backups. This poses high risk if an AI agent mistakenly targets the wrong layer or field.
From the tool's definition Tool name 'fl_delete_fields' indicates permanent deletion of fields from a feature layer; no description provided but the prefix 'fl_' suggests feature layer operations, and 'delete_fields' explicitly denotes removal of schema elements that cannot be undone.
Attacks that exploit this kind of access
fl_delete_fields. 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 fl_delete_fields: 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.
fl_delete_fields 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 fl_delete_fields 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 fl_delete_fields. 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.
fl_delete_fields 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 →