gp_run_with_env · ArcGIS MCP: Risk & Policy

WHAT IT DOES

What gp_run_with_env does on ArcGIS MCP

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

WHY IT NEEDS A POLICY

Why gp_run_with_env needs a policy

Geoprocessing execution tools trigger external operations whose effects depend on provided arguments (task selection, parameters, environment variables). This fits the Execute category: runs code or triggers external operations. Severity is high because geoprocessing jobs can consume resources, modify data in connected services, or produce unintended spatial analysis results depending on how arguments are crafted.

From the tool's definition Tool name 'gp_run_with_env' indicates execution of geoprocessing tasks with environment variables. The 'gp_' prefix and 'run_with_env' suffix strongly suggest dynamic code/task execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gp_run_with_env Rate-limited

gp_run_with_env 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": {
    "gp_run_with_env": {
      "limits": [
        {
          "counter": "gp_run_with_env_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 ArcGIS MCP, so you can run agents against it safely.

FAQ

Questions about gp_run_with_env

What does the gp_run_with_env tool do? +

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

How do I enforce a policy on gp_run_with_env? +

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

What risk level is gp_run_with_env? +

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

Can I rate-limit gp_run_with_env? +

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

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

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