query_zones

SERVERKiCAD-MCP-Server SOURCEmixelpixx/kicad-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mixelpixx-kicad-mcp-server/query-zones.md

WHAT IT DOES

What query_zones does on KiCAD-MCP-Server

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

RISK

Why query_zones is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs query_zones safely

PolicyLayer is an MCP gateway: it sits between your AI agents and KiCAD-MCP-Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For query_zones, this is the rule to start with:

query_zones Allowed

query_zones is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_zones": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect KiCAD-MCP-Server, apply this rule, and every query_zones call is checked against it from then on.

FAQ

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.

KEEP EXPLORING

More on KiCAD-MCP-Server, and thousands of servers like it.

This server

All 231 KiCAD-MCP-Server tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →