save_as

Save the current PCB board to a new .kicad_pcb path.

SERVERKiCAD-MCP-Server SOURCEmixelpixx/kicad-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mixelpixx-kicad-mcp-server/save-as.md

WHAT IT DOES

What save_as does on KiCAD-MCP-Server

AI agents use save_as 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.

RISK

Why save_as is rated Medium

The save_as operation creates or overwrites a file in the filesystem. While file creation/modification is typically Write category, the severity is elevated to medium rather than low because: (1) it can overwrite existing files without explicit confirmation, (2) in an automated/agentic context, unintended file creation in wrong paths could cause confusion or storage issues, and (3) it modifies persistent design data.

From the tool's definition Tool description states "Save the current PCB board to a new .kicad_pcb path" — this creates or modifies a file by saving to a new location, which is a reversible write operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

save_as Rate-limited

save_as 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_as": {
      "limits": [
        {
          "counter": "save_as_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about save_as

What does the save_as tool do? +

Save the current PCB board to a new .kicad_pcb path. 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.

How do I enforce a policy on save_as? +

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

save_as is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit save_as? +

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

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

save_as 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

save_snapshot on Why Did You Render → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →