select_by_attribute · Arcmap MCP: Risk & Policy

WHAT IT DOES

What select_by_attribute does on Arcmap

AI agents invoke select_by_attribute 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.

WHY IT NEEDS A POLICY

Why select_by_attribute needs a policy

The tool executes an SQL query to select features in a live ArcMap session and refreshes the display. This is not a pure read (it modifies the active selection state and triggers a refresh), but it doesn't irreversibly delete or overwrite data. It falls under Execute because it runs SQL expressions against live GIS data and triggers external operations (selection state change, canvas refresh).

From the tool's definition 'Selecciona entidades de una capa por SQL (NEW_SELECTION) y refresca' — executes an SQL-based selection query against a live ArcMap session and triggers a canvas refresh

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

select_by_attribute Rate-limited

select_by_attribute stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "select_by_attribute": {
      "limits": [
        {
          "counter": "select_by_attribute_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Arcmap, so you can run agents against it safely.

FAQ

Questions about select_by_attribute

What does the select_by_attribute tool do? +

Selecciona entidades de una capa por SQL (NEW_SELECTION) y refresca. 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.

How do I enforce a policy on select_by_attribute? +

Register the Arcmap MCP server in PolicyLayer and add a rule for select_by_attribute: 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.

What risk level is select_by_attribute? +

select_by_attribute is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit select_by_attribute? +

Yes. Add a rate_limit block to the select_by_attribute 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.

How do I block select_by_attribute completely? +

Set action: deny in the PolicyLayer policy for select_by_attribute. 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.

What MCP server provides select_by_attribute? +

select_by_attribute 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.