Save a named checkpoint snapshot of the current project state (renders board to PDF and records step label). Call after completing each major step — e.g. after Step 1 (schematic_ok) and Step 2 (layout_ok). Required by the demo workflow before waiting for user confirmation.
AI agents use snapshot_project 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.
This tool saves/writes a snapshot and renders a PDF — it creates new data (checkpoint files, PDF renders) without irreversibly deleting anything. It is a Write operation with medium severity since it modifies project state by adding snapshot files, but does not delete or overwrite existing data.
From the tool's definition Save a named checkpoint snapshot of the current project state (renders board to PDF and records step label)
Documented attack patterns abuse exactly the kind of access snapshot_project 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 snapshot_project:
{
"version": "1",
"default": "deny",
"tools": {
"snapshot_project": {
"limits": [
{
"counter": "snapshot_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}snapshot_project stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Save a named checkpoint snapshot of the current project state (renders board to PDF and records step label). Call after completing each major step — e.g. after Step 1 (schematic_ok) and Step 2 (layout_ok). Required by the demo workflow before waiting for user confirmation. It is categorised as a Write tool in the KiCAD-MCP-Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the KiCAD-MCP-Server MCP server in PolicyLayer and add a rule for snapshot_project: 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.
snapshot_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the snapshot_project 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 snapshot_project. 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.
snapshot_project 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.