Execute arbitrary PyQGIS code provided as a string.
AI agents invoke execute_code to trigger actions in QGISMCP. 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.
This tool allows execution of arbitrary Python code within the QGIS environment. While not immediately destructive (data could be backed up), it grants full programmatic control over QGIS and potentially the underlying system. Misuse could modify projects, corrupt data, or access sensitive information. The blast radius is significant—an AI agent could be tricked into executing malicious code.
From the tool's definition Tool name is 'execute_code' and description states 'Execute arbitrary PyQGIS code provided as a string.' The word 'arbitrary' and 'Execute' directly indicate arbitrary code execution capability.
Documented attack patterns abuse exactly the kind of access execute_code gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and QGISMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_code:
{
"version": "1",
"default": "deny",
"tools": {
"execute_code": {
"limits": [
{
"counter": "execute_code_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_code 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.
Free to start. No card required.
Execute arbitrary PyQGIS code provided as a string. It is categorised as a Execute tool in the QGISMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the QGIS MCP server in PolicyLayer and add a rule for execute_code: 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 QGISMCP. Nothing to install.
execute_code is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_code 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.
Set action: deny in the PolicyLayer policy for execute_code. 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.
execute_code is provided by the QGIS MCP server (syauqi-uqi/qgis_mcp_modify1). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from QGISMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 QGISMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.