notebook_execute · ArcGIS MCP: Risk & Policy

WHAT IT DOES

What notebook_execute does on ArcGIS MCP

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

Executing arbitrary notebook code is a classic Execute risk—it can trigger external operations, modify system state, and access server resources depending on what code is submitted. The empty description reduces confidence slightly, but the name and server context are clear enough.

From the tool's definition Tool name 'notebook_execute' indicates execution of notebook code; description is empty but the function name and ArcGIS context (which supports Python notebooks) strongly suggest runtime code execution on the server.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

notebook_execute Rate-limited

notebook_execute 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": {
    "notebook_execute": {
      "limits": [
        {
          "counter": "notebook_execute_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 notebook_execute

What does the notebook_execute tool do? +

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

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

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

Can I rate-limit notebook_execute? +

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

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

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