execute_processing_batch · QGIS MCP: Risk & Policy

WHAT IT DOES

What execute_processing_batch does on QGIS MCP

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

This tool directly executes QGIS processing algorithms in a loop over multiple parameter sets. The effects are determined by which algorithm is selected and what parameters are passed, making it impossible to predict outcomes statically. While some algorithms may be read-only (like 'buffer analysis'), others can destructively transform data or trigger external operations.

From the tool's definition Tool name is 'execute_processing_batch' and description states 'Run one algorithm once per parameter dict in' — indicates execution of processing algorithms with batch parameters.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_processing_batch Rate-limited

execute_processing_batch 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_batch": {
      "limits": [
        {
          "counter": "execute_processing_batch_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_batch

What does the execute_processing_batch tool do? +

Run one algorithm once per parameter dict in. 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_batch? +

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

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

Can I rate-limit execute_processing_batch? +

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

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

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