This record as markdown: /tools/eda-agent/pcb-remove-teardrops.md
What pcb_remove_teardrops does on Eda Agent
AI agents call pcb_remove_teardrops 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_remove_teardrops is rated Critical
This tool irreversibly removes teardrops from the entire PCB board. The 'board-wide' scope means it affects all teardrops across the entire design in one operation, making it a broad destructive action that modifies PCB geometry. While teardrops can potentially be re-added, the removal itself is a destructive modification to the design data.
From the tool's definition Remove teardrops board-wide
Attacks that exploit this kind of access
The rule that runs pcb_remove_teardrops 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_remove_teardrops, this is the rule to start with:
pcb_remove_teardrops 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_remove_teardrops call is checked against it from then on.
Questions about pcb_remove_teardrops
Remove teardrops board-wide. 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_remove_teardrops: 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_remove_teardrops 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_remove_teardrops 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_remove_teardrops. 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_remove_teardrops 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