execute_processing · QGIS MCP: Risk & Policy

WHAT IT DOES

What execute_processing does on QGIS MCP

AI agents invoke execute_processing to trigger actions in QGIS 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 execute_processing needs a policy

This tool allows execution of arbitrary QGIS Processing algorithms, which are user-specified operations whose effects depend on the arguments (algorithm selection and parameters). While some algorithms may be read-only (Read category), many perform GIS computations, data modifications, and external tool triggers (Execute category).

From the tool's definition Tool name is 'execute_processing' and description states it 'Execute[s] a QGIS Processing algorithm'. QGIS Processing algorithms can perform a wide variety of operations including geospatial computations, data transformations, and external tool invocations…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_processing Rate-limited

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

FAQ

Questions about execute_processing

What does the execute_processing tool do? +

Execute a QGIS Processing algorithm. Use get_algorithm_help to discover parameters. It is categorised as a Execute tool in the QGIS 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 execute_processing? +

Register the QGIS MCP server in PolicyLayer and add a rule for execute_processing: 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 QGIS MCP. Nothing to install.

What risk level is execute_processing? +

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

Can I rate-limit execute_processing? +

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

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

execute_processing is provided by the QGIS MCP server (nkarasiak/qgis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.