remove_library_table_entry
Remove one or more entries from a sym-lib-table or fp-lib-table by nickname — the
This record as markdown: /tools/mixelpixx-kicad-mcp-server/remove-library-table-entry.md
What remove_library_table_entry does on KiCAD-MCP-Server
AI agents call remove_library_table_entry to permanently remove resources in KiCAD-MCP-Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_library_table_entry is rated Critical
Irreversibly deletes library configuration entries; cannot be undone without manual restoration or version control.
From the tool's definition Remove one or more entries from a sym-lib-table or fp-lib-table
Attacks that exploit this kind of access
The rule that runs remove_library_table_entry 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 remove_library_table_entry, this is the rule to start with:
remove_library_table_entry is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect KiCAD-MCP-Server, apply this rule, and every remove_library_table_entry call is checked against it from then on.
Questions about remove_library_table_entry
Remove one or more entries from a sym-lib-table or fp-lib-table by nickname — the. It is categorised as a Destructive tool in the KiCAD-MCP-Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the KiCAD-MCP-Server MCP server in PolicyLayer and add a rule for remove_library_table_entry: 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.
remove_library_table_entry is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_library_table_entry 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 remove_library_table_entry. 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.
remove_library_table_entry 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.
Across the catalogue