batch_geocode
AI agents invoke batch_geocode 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.
Batch geocoding triggers an external geoprocessing operation against an address database or geocoding service. It's not a simple read (it submits data and invokes processing), not purely destructive or financial. Execute is the best fit. Confidence is low due to empty description — the tool could also be Write if it stores results, but Execute covers the external operation aspect.
From the tool's definition Tool name 'batch_geocode' and empty description. Geocoding converts addresses to coordinates, which typically involves calling an external geocoding service/operation.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
batch_geocode. 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 batch_geocode: 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.
batch_geocode 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 batch_geocode 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 batch_geocode. 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.
batch_geocode 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 →