pcb_delete_invalid_objects
Remove degenerate primitives from the active PCB.
This record as markdown: /tools/eda-agent/pcb-delete-invalid-objects.md
What pcb_delete_invalid_objects does on Eda Agent
AI agents call pcb_delete_invalid_objects to permanently remove resources in Eda Agent, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why pcb_delete_invalid_objects is rated Critical
The tool deletes PCB primitives, which is an irreversible operation that cannot be easily undone programmatically by an AI agent. While the objects targeted are 'degenerate' (malformed), the deletion itself is destructive. An agent misusing this could remove valid-but-unusual primitives, corrupting a PCB design. This is more severe than Write (reversible modification) and ranks as Destructive.
From the tool's definition Tool name contains 'delete' and description states 'Remove degenerate primitives from the active PCB' — this irreversibly removes objects from a design artifact.
Attacks that exploit this kind of access
The rule that runs pcb_delete_invalid_objects safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Eda Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pcb_delete_invalid_objects, this is the rule to start with:
pcb_delete_invalid_objects 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 Eda Agent, apply this rule, and every pcb_delete_invalid_objects call is checked against it from then on.
Questions about pcb_delete_invalid_objects
Remove degenerate primitives from the active PCB. It is categorised as a Destructive tool in the Eda Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Eda Agent MCP server in PolicyLayer and add a rule for pcb_delete_invalid_objects: 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 Eda Agent. Nothing to install.
pcb_delete_invalid_objects 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 pcb_delete_invalid_objects 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 pcb_delete_invalid_objects. 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.
pcb_delete_invalid_objects is provided by the Eda Agent MCP server (salitronic/eda-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Eda Agent, and thousands of servers like it.
Across the catalogue