execute_processing

THE RISK

High Risk

Why execute_processing needs a policy

This tool executes external processing algorithms with user-controlled parameters. While not as severe as direct code execution (execute_code), it still runs algorithms whose side effects are argument-dependent and could potentially modify project state, trigger external operations, or consume resources.

From the tool's definition Tool name 'execute_processing' combined with description 'Execute a processing algorithm with the given parameters' indicates runtime code/algorithm execution. The sibling tool 'execute_code' on the same server confirms this is an execution-capable server.

Documented attack patterns abuse exactly the kind of access execute_processing gives an agent:

POLICY

How to control execute_processing

PolicyLayer is an MCP gateway — it sits between your AI agents and QGIS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_processing:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_processing": {
      "limits": [
        {
          "counter": "execute_processing_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

Create a free account and register QGIS MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More QGIS MCP Server tools

Destructive remove_layer Remove a layer from the project by its ID. Execute execute_code Execute arbitrary PyQGIS code provided as a string. Execute zoom_to_layer Zoom to the extent of a specified layer. Write load_project Load a QGIS project from the specified path. Write render_map Render the current map view to an image file with the specified dimensions. Write add_raster_layer Add a raster layer to the project. Write add_vector_layer Add a vector layer to the project. Write create_new_project Create a new project a save it

All 15 QGIS MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in QGIS MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about execute_processing

What does the execute_processing tool do? +

Execute a processing algorithm with the given parameters. It is categorised as a Execute tool in the QGIS MCP Server 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 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 Server. 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 MCP server (jjsantos01/qgis_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every QGIS MCP Server tool call.

Start from QGIS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →