AI agents use add_layout_label to create or update resources in QGIS MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QGIS MCP environment.
Adding a layout label creates new content in a QGIS print layout, making it a Write operation (reversible modification). The severity is medium because: (1) the blast radius is limited to the print layout itself, not underlying geospatial data; (2) the action is easily reversible by deleting the label; (3) there is no direct financial impact or data destruction.
From the tool's definition The tool 'add_layout_label' creates new text elements in a print layout by adding a label with specified text content. This is a creation operation that modifies the print layout document reversibly.
Attacks that exploit this kind of access
Add a text label to a print layout (mm). text may contain [% expression %]. It is categorised as a Write tool in the QGIS MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the QGIS MCP server in PolicyLayer and add a rule for add_layout_label: 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.
add_layout_label is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_layout_label 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 add_layout_label. 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.
add_layout_label 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →