Low Risk

query_traces

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

How to control query_traces ↓

What query_traces does on KiCAD-MCP-Server

AI agents call query_traces 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_traces needs a policy

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.

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

How to control query_traces

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

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

query_traces 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_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.

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.