rename_field · QGIS MCP: Risk & Policy

WHAT IT DOES

What rename_field does on QGIS MCP

AI agents use rename_field 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.

WHY IT NEEDS A POLICY

Why rename_field needs a policy

This tool modifies schema metadata (field names) in a vector layer, which is a reversible write operation. While the change affects the data structure, it does not delete data, execute arbitrary code, or cause destructive effects. The severity is medium because renaming fields could break dependent workflows or references if done incorrectly by an agent, but the operation is undoable through another rename.

From the tool's definition Tool name is 'rename_field' and description states it will 'Rename a field in a vector layer.' Renaming is a reversible modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_field Rate-limited

rename_field stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename_field": {
      "limits": [
        {
          "counter": "rename_field_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 rename_field

What does the rename_field tool do? +

Rename a field in a vector layer. 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.

How do I enforce a policy on rename_field? +

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

rename_field is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rename_field? +

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

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

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