fset_statistics
AI agents call fset_statistics 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.
Given the empty description, confidence is moderate. The name suggests data retrieval (statistics calculation on a feature set) with no modification, deletion, or execution of arbitrary code. However, lack of documentation creates uncertainty about actual implementation. Categorized as Read as the most likely intent, with severity low due to typical read-only nature of statistical queries.
From the tool's definition Tool name 'fset_statistics' suggests retrieval of statistics; no description provided. Based on naming convention and context within ArcGIS (where 'fset' likely refers to feature set and 'statistics' implies aggregation/reporting), this appears to be a query…
Attacks that exploit this kind of access
fset_statistics. 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_statistics: 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_statistics 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_statistics 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_statistics. 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_statistics 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 →