lib_delete_component

A destructive tool on the Altium-MCP-Suite MCP server.

SERVERAltium-MCP-Suite SOURCEM-R-Abedini/Altium-MCP-Suite

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/altium-mcp-suite/lib-delete-component.md

WHAT IT DOES

What lib_delete_component does on Altium-MCP-Suite

AI agents call lib_delete_component 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.

RISK

Why lib_delete_component is rated Critical

Deletes component library data permanently without undo; blocks design automation workflows.

From the tool's definition lib_delete_component performs irreversible deletion of library components.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs lib_delete_component 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 lib_delete_component, this is the rule to start with:

lib_delete_component Hidden

lib_delete_component is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "lib_delete_component"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Altium-MCP-Suite, apply this rule, and every lib_delete_component call is checked against it from then on.

FAQ

Questions about lib_delete_component

What does the lib_delete_component tool do? +

lib_delete_component 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.

How do I enforce a policy on lib_delete_component? +

Register the Altium-MCP-Suite MCP server in PolicyLayer and add a rule for lib_delete_component: 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.

What risk level is lib_delete_component? +

lib_delete_component is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit lib_delete_component? +

Yes. Add a rate_limit block to the lib_delete_component 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.

How do I block lib_delete_component completely? +

Set action: deny in the PolicyLayer policy for lib_delete_component. 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.

What MCP server provides lib_delete_component? +

lib_delete_component 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.

KEEP EXPLORING

More on Altium-MCP-Suite, and thousands of servers like it.

This server

All 817 Altium-MCP-Suite tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →