fl_create_view
AI agents use fl_create_view 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 'create' action in the tool name indicates a write operation that establishes a new resource (likely a feature layer view). This is reversible (views can be deleted) and has moderate blast radius if an AI agent creates unwanted views, polluting the geospatial catalog or consuming resources.
From the tool's definition Tool name 'fl_create_view' suggests creating a feature layer view. No description provided, but 'create' indicates data/resource generation. Context shows this is part of ArcGIS feature layer management tools.
Attacks that exploit this kind of access
fl_create_view. 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 fl_create_view: 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_create_view 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 fl_create_view 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_create_view. 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_create_view 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 →