run_geoprocessing · Arcmap MCP: Risk & Policy

WHAT IT DOES

What run_geoprocessing does on Arcmap

AI agents invoke run_geoprocessing 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 run_geoprocessing needs a policy

Geoprocessing operations can perform complex spatial transformations, modify data, and trigger external geospatial operations. Without a description to constrain scope, and given the arcpy execution context, this tool should be classified as Execute rather than Write because geoprocessing tools often have irreversible effects (e.g., spatial transformations, rasterization, feature generalization) and side effects…

From the tool's definition Tool named 'run_geoprocessing' on an ArcMap MCP server where sibling tools include 'execute_arcpy' and the server description explicitly mentions 'allows AI agents to control a live ArcMap session via arcpy'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_geoprocessing Rate-limited

run_geoprocessing 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": {
    "run_geoprocessing": {
      "limits": [
        {
          "counter": "run_geoprocessing_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 run_geoprocessing

What does the run_geoprocessing tool do? +

run_geoprocessing. 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 run_geoprocessing? +

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

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

Can I rate-limit run_geoprocessing? +

Yes. Add a rate_limit block to the run_geoprocessing 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 run_geoprocessing completely? +

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

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