# sync_schematic_to_board

Import the schematic netlist into the PCB board — equivalent to pressing F8 in KiCAD (Tools → Update PCB from Schematic). MUST be called after the schematic is complete and before placing or routing components on the PCB. Without this step, the board has no footprints and no net assignments — place_component and route_pad_to_pad will produce an empty, unroutable board.

Agent View of the PolicyLayer registry record for `sync_schematic_to_board`. HTML page: https://policylayer.com/tools/mixelpixx-kicad-mcp-server/sync-schematic-to-board

## Facts

- Tool: `sync_schematic_to_board`
- Server: KiCAD-MCP-Server (`mixelpixx/kicad-mcp-server`) — https://policylayer.com/tools/mixelpixx-kicad-mcp-server.md
- Homepage: https://github.com/mixelpixx/KiCAD-MCP-Server
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "sync_schematic_to_board",
    "arguments": {}
  }
}
```

## Why sync_schematic_to_board is rated Medium

This tool creates or modifies PCB board data (footprints, net assignments) in a reversible manner. While the effects are significant (the tool notes that without it 'the board has no footprints and no net assignments'), the operation is not destructive—the netlist can be re-imported or the board state can be reset. It does not execute arbitrary code, delete data irreversibly, or move money.

From the tool's own definition: "Tool description explicitly states it 'Import[s] the schematic netlist into the PCB board' and performs an update operation equivalent to 'Update PCB from Schematic'. This modifies the PCB board state by adding footprints and net assignments."

## Use case

AI agents use sync_schematic_to_board to create or update resources in KiCAD-MCP-Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your KiCAD-MCP-Server environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches KiCAD-MCP-Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "sync_schematic_to_board": {
      "limits": [
        {
          "counter": "sync_schematic_to_board_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on KiCAD-MCP-Server (230)

- `clear_board_outline` — Destructive — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/clear-board-outline.md
- `delete_component` — Destructive — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/delete-component.md
- `delete_graphic` — Destructive — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/delete-graphic.md
- `delete_schematic_component` — Destructive — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/delete-schematic-component.md
- `delete_schematic_net_label` — Destructive — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/delete-schematic-net-label.md
- `delete_schematic_wire` — Destructive — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/delete-schematic-wire.md
- `delete_symbol` — Destructive — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/delete-symbol.md
- `delete_trace` — Destructive — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/delete-trace.md
- `discard_or_reload` — Destructive — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/discard-or-reload.md
- `remove_hierarchical_sheet` — Destructive — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/remove-hierarchical-sheet.md
- `remove_library_table_entry` — Destructive — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/remove-library-table-entry.md
- `remove_schematic_component_property` — Destructive — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/remove-schematic-component-property.md
- `autoroute` — Execute — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/autoroute.md
- `export_3d_cli` — Execute — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/export-3d-cli.md
- `export_drill` — Execute — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/export-drill.md
- `launch_kicad_ui` — Execute — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/launch-kicad-ui.md
- `refill_zones` — Execute — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/refill-zones.md
- `run_drc` — Execute — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/run-drc.md
- `run_erc` — Execute — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/run-erc.md
- `batch_list_symbol_pins` — Read — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/batch-list-symbol-pins.md
- `check_clearance` — Read — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/check-clearance.md
- `check_courtyard_overlaps` — Read — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/check-courtyard-overlaps.md
- `check_freerouting` — Read — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/check-freerouting.md
- `check_kicad_ui` — Read — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/check-kicad-ui.md
- `check_placement_clearance` — Read — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/check-placement-clearance.md
- `download_registry_part` — Read — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/download-registry-part.md
- `estimate_airwire_lengths` — Read — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/estimate-airwire-lengths.md
- `export_bom` — Read — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/export-bom.md
- `export_ipc2581` — Read — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/export-ipc2581.md
- `export_ipcd356` — Read — https://policylayer.com/tools/mixelpixx-kicad-mcp-server/export-ipcd356.md
- …and 200 more: https://policylayer.com/tools/mixelpixx-kicad-mcp-server.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=mixelpixx-kicad-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/mixelpixx-kicad-mcp-server