Low Risk

get_layers

Retrieve all layers in the current project.

How to control get_layers ↓

What get_layers does on QGISMCP

AI agents call get_layers to retrieve information from QGISMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_layers needs a policy

This tool performs a retrieval/query operation to list or fetch existing layers from a QGIS project. It has no capability to modify, execute operations, or cause destructive changes. The blast radius of misuse is minimal since it only exposes read-only metadata about the project structure.

From the tool's definition Tool name is 'get_layers' and description states 'Retrieve all layers in the current project' - this is a read-only query operation with no data modification or side effects.

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

How to control get_layers

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 get_layers:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_layers": {}
  }
}

get_layers is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register QGISMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_layers

What does the get_layers tool do? +

Retrieve all layers in the current project. It is categorised as a Read tool in the QGISMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_layers? +

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

What risk level is get_layers? +

get_layers is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_layers? +

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

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

get_layers is provided by the QGIS MCP server (kicker315/deepseek_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 QGISMCP tool call.

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.

17 QGISMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.