fset_to_geojson
AI agents call fset_to_geojson to retrieve information from ArcGIS MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to convert feature set data into GeoJSON output format, which is a read/retrieval operation with no side effects on the source data. However, confidence is moderate (0.7) due to the empty description—if this tool were to write converted data back to a feature layer or delete the original feature set, the classification would change to Write or Destructive.
From the tool's definition Tool name 'fset_to_geojson' suggests conversion of a feature set to GeoJSON format. The 'to' prefix and 'geojson' output format indicate data transformation/retrieval rather than creation or modification of underlying data.
Attacks that exploit this kind of access
fset_to_geojson. It is categorised as a Read tool in the ArcGIS MCP MCP Server, which means it retrieves data without modifying state.
Register the ArcGIS MCP server in PolicyLayer and add a rule for fset_to_geojson: 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.
fset_to_geojson is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fset_to_geojson 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 fset_to_geojson. 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.
fset_to_geojson 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 →