Low Risk

query_zones

Query copper zones (filled pours) on the board with optional filters by net, layer, or bounding box. Returns zone net, layers, priority, fill state, and bounding box. Useful for auditing power planes and GND pours that query_traces does not include.

How to control query_zones ↓

What query_zones does on KiCAD-MCP-Server

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

Low Risk

Why query_zones needs a policy

query_zones retrieves and inspects existing board design metadata (copper zone properties). It has no side effects, does not modify the PCB design, and does not execute arbitrary code or trigger external actions. This is a straightforward read operation for auditing purposes.

From the tool's definition Tool description states it 'Query[ies] copper zones' and 'Returns zone net, layers, priority, fill state, and bounding box.' The verb 'query' combined with 'returns' data indicates retrieval only.

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

How to control query_zones

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

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

query_zones 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 KiCAD-MCP-Server — 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 query_zones

What does the query_zones tool do? +

Query copper zones (filled pours) on the board with optional filters by net, layer, or bounding box. Returns zone net, layers, priority, fill state, and bounding box. Useful for auditing power planes and GND pours that query_traces does not include. It is categorised as a Read tool in the KiCAD-MCP-Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_zones? +

Register the KiCAD-MCP-Server MCP server in PolicyLayer and add a rule for query_zones: 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 KiCAD-MCP-Server. Nothing to install.

What risk level is query_zones? +

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

Can I rate-limit query_zones? +

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

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

query_zones is provided by the KiCAD-MCP-Server MCP server (mixelpixx/kicad-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every KiCAD-MCP-Server tool call.

Start from KiCAD-MCP-Server, 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.

157 KiCAD-MCP-Server 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.