Check the actual clearance between two PCB items (track, via, pad, zone or component) and report whether it meets the design rules.
AI agents call check_clearance 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.
This tool queries and validates existing PCB design data against rules. It retrieves clearance information and produces a report, matching the Read category pattern of data retrieval with no side effects. No data is created, modified, deleted, or executed. The context (PCB design validation) and sibling tools (which add components, layers, etc.) confirm this is a diagnostic/verification function.
From the tool's definition Tool description states it 'Check[s] the actual clearance' and 'report[s] whether it meets the design rules' — purely informational operations with no modifications or side effects.
Documented attack patterns abuse exactly the kind of access check_clearance gives an agent:
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 check_clearance:
{
"version": "1",
"default": "deny",
"tools": {
"check_clearance": {}
}
} check_clearance is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check the actual clearance between two PCB items (track, via, pad, zone or component) and report whether it meets the design rules. It is categorised as a Read tool in the KiCAD-MCP-Server MCP Server, which means it retrieves data without modifying state.
Register the KiCAD-MCP-Server MCP server in PolicyLayer and add a rule for check_clearance: 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.
check_clearance is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_clearance 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.
Set action: deny in the PolicyLayer policy for check_clearance. 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.
check_clearance 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.
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.