query_traces

Query traces on the board with optional filters by net, layer, or bounding box.

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-traces.md

WHAT IT DOES

What query_traces does on KiCAD-MCP-Server

AI agents call query_traces 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_traces is rated Low

This tool performs read-only operations to retrieve trace information from a KiCAD board design. It accepts filter parameters (net, layer, bounding box) but does not create, modify, delete, or execute any external operations. The action is purely informational retrieval, which is the definition of the Read category.

From the tool's definition Tool name is 'query_traces' and description states it 'Query traces on the board with optional filters by net, layer, or bounding box' — the verb 'query' combined with 'optional filters' indicates data retrieval with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs query_traces 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_traces, this is the rule to start with:

query_traces Allowed

query_traces 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_traces": {}
  }
}

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_traces call is checked against it from then on.

FAQ

Questions about query_traces

What does the query_traces tool do? +

Query traces on the board with optional filters by net, layer, or bounding box. 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_traces? +

Register the KiCAD-MCP-Server MCP server in PolicyLayer and add a rule for query_traces: 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_traces? +

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

Can I rate-limit query_traces? +

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

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

query_traces 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 →