geometry_buffer
AI agents invoke geometry_buffer to trigger actions in ArcGIS MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Buffering geometry typically involves running a geoprocessing computation on spatial data. Given the server description mentions geoprocessing tools, this likely executes a spatial operation. Without a description, confidence is low, but the name suggests an Execute-category geoprocessing task rather than a simple read or destructive action.
From the tool's definition Tool name 'geometry_buffer' suggests a geoprocessing operation that computes a buffer zone around geometries. Description is empty and uninformative.
Attacks that exploit this kind of access
geometry_buffer. It is categorised as a Execute tool in the ArcGIS MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ArcGIS MCP server in PolicyLayer and add a rule for geometry_buffer: 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.
geometry_buffer is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the geometry_buffer 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 geometry_buffer. 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.
geometry_buffer 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 →