gp_run_async · ArcGIS MCP: Risk & Policy

WHAT IT DOES

What gp_run_async does on ArcGIS MCP

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

Geoprocessing tools execute external operations whose effects depend on arguments. The async execution pattern indicates the tool triggers computational tasks on a remote server. While description is absent (lowering confidence slightly), the naming convention and server context (ArcGIS with geoprocessing capability) clearly indicate this runs code/processes.

From the tool's definition Tool name 'gp_run_async' indicates geoprocessing execution (gp_ prefix), async pattern suggests running asynchronous operations. Description is empty, limiting specificity.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gp_run_async Rate-limited

gp_run_async 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_async": {
      "limits": [
        {
          "counter": "gp_run_async_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_async

What does the gp_run_async tool do? +

gp_run_async. 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_async? +

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

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

Can I rate-limit gp_run_async? +

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

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

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