rename_symbol
Rename a symbol in a .kicad_sym library, including its sub-symbol shards (name_0_1, ...) and
This record as markdown: /tools/mixelpixx-kicad-mcp-server/rename-symbol.md
What rename_symbol does on KiCAD-MCP-Server
AI agents use rename_symbol 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.
Why rename_symbol is rated Medium
This tool modifies symbol names in KiCAD library files, which is a reversible write operation. It does not create new data (that would be Execute/Write for circuit design), nor does it delete or irreversibly destroy symbols. The medium severity reflects that renaming symbols across a library could impact design references if done incorrectly, but the change is not destructive and can be undone.
From the tool's definition Tool name 'rename_symbol' and description 'Rename a symbol in a .kicad_sym library' indicate modification of existing data. The action is reversible (a symbol can be renamed again), and affects metadata/naming rather than creation or deletion.
Attacks that exploit this kind of access
The rule that runs rename_symbol 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 rename_symbol, this is the rule to start with:
rename_symbol 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.
The button opens the PolicyLayer dashboard: create your workspace, connect KiCAD-MCP-Server, apply this rule, and every rename_symbol call is checked against it from then on.
Questions about rename_symbol
Rename a symbol in a .kicad_sym library, including its sub-symbol shards (name_0_1, ...) and. 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 rename_symbol: 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.
rename_symbol 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 rename_symbol 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 rename_symbol. 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.
rename_symbol 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.
More on KiCAD-MCP-Server, and thousands of servers like it.
This server
Across the catalogue