obj_delete
A destructive tool on the Altium-MCP-Suite MCP server.
This record as markdown: /tools/altium-mcp-suite/obj-delete.md
What obj_delete does on Altium-MCP-Suite
AI agents call obj_delete to permanently remove resources in Altium-MCP-Suite, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why obj_delete is rated Critical
The name 'obj_delete' strongly implies an irreversible deletion operation. Despite the empty description, the semantic meaning of 'delete' combined with the server's purpose (design automation where objects are schematic elements, PCB traces/components, or library items) indicates this is a Destructive action. An AI agent misusing this could permanently remove critical design work.
From the tool's definition Tool name is 'obj_delete' which indicates deletion of objects. In the context of an Altium Designer automation server with 290+ tools for schematic, PCB, library & project automation, this would irreversibly remove design elements (schematic objects, PCB…
Attacks that exploit this kind of access
The rule that runs obj_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Altium-MCP-Suite, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For obj_delete, this is the rule to start with:
obj_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 Altium-MCP-Suite, apply this rule, and every obj_delete call is checked against it from then on.
Questions about obj_delete
obj_delete is a destructive tool on the Altium-MCP-Suite MCP server. It is categorised as a Destructive tool in the Altium-MCP-Suite MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Altium-MCP-Suite MCP server in PolicyLayer and add a rule for obj_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 Altium-MCP-Suite. Nothing to install.
obj_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_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_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_delete is provided by the Altium-MCP-Suite MCP server (M-R-Abedini/Altium-MCP-Suite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Altium-MCP-Suite, and thousands of servers like it.
Across the catalogue