fl_attachment_add
AI agents use fl_attachment_add 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 tool name suggests adding attachments to feature layer items in ArcGIS, which is a reversible write operation that creates or modifies data. It does not delete, execute arbitrary code, or involve financial transactions. Medium severity reflects that uncontrolled attachment uploads could consume storage or introduce malicious files, but the operation remains reversible.
From the tool's definition Tool name 'fl_attachment_add' contains 'add' which indicates creating/adding data to a feature layer attachment. Description is empty, preventing full analysis.
Attacks that exploit this kind of access
fl_attachment_add. 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_attachment_add: 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_attachment_add 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_attachment_add 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_attachment_add. 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_attachment_add 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 →