obj_batch_delete
A destructive tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/obj-batch-delete.md
What obj_batch_delete does on Eda Agent
AI agents call obj_batch_delete 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 obj_batch_delete is rated Critical
The name 'obj_batch_delete' clearly indicates bulk deletion of objects without ability to undo within the tool itself. In the context of Altium Designer automation (schematic, PCB, library components), batch deletion of design objects is irreversible and could destroy significant work. This is a destructive operation with high blast radius if invoked incorrectly by an AI agent.
From the tool's definition Tool name 'obj_batch_delete' contains 'delete' and 'batch', indicating irreversible deletion of multiple objects. Description is empty, limiting certainty but not changing the classification.
Attacks that exploit this kind of access
The rule that runs obj_batch_delete 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 obj_batch_delete, this is the rule to start with:
obj_batch_delete 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 obj_batch_delete call is checked against it from then on.
Questions about obj_batch_delete
obj_batch_delete is a destructive tool on the Eda Agent MCP server. 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 obj_batch_delete: 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.
obj_batch_delete 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 obj_batch_delete 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 obj_batch_delete. 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.
obj_batch_delete 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