AI agents invoke zoom_to_layer to trigger actions in Arcmap. 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.
This tool manipulates a live ArcMap session by zooming to a layer extent and refreshing the canvas. It doesn't just read data — it executes an action on an external application (ArcMap). It's not destructive or financial, but it does trigger an operation in the live session, making it Execute. Blast radius is low since it only affects the view state of the map.
From the tool's definition 'Encuadra el mapa al extent de una capa' (frames/zooms the map to a layer extent) and 'refresca el canvas vivo' (refreshes the live canvas) — triggers an external operation on a live ArcMap session
Attacks that exploit this kind of access
Encuadra el mapa al extent de una capa por nombre y refresca el canvas vivo. It is categorised as a Execute tool in the Arcmap MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Arcmap MCP server in PolicyLayer and add a rule for zoom_to_layer: 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 Arcmap. Nothing to install.
zoom_to_layer 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 zoom_to_layer 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 zoom_to_layer. 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.
zoom_to_layer is provided by the Arcmap MCP server (pedralcg/arcmap-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 →