lib_uninstall_library
Unregister a library from the environment's Available Libraries.
This record as markdown: /tools/eda-agent/lib-uninstall-library.md
What lib_uninstall_library does on Eda Agent
AI agents call lib_uninstall_library 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 lib_uninstall_library is rated Critical
Unregistering/uninstalling a library from the design environment is a destructive action that removes configuration state and availability. While not deleting data files, it irreversibly severs the library from the active environment and can cause cascading failures in projects referencing that library.
From the tool's definition The tool name 'lib_uninstall_library' combined with the description 'Unregister a library from the environment's Available Libraries' indicates irreversible removal of a library registration.
Attacks that exploit this kind of access
The rule that runs lib_uninstall_library 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 lib_uninstall_library, this is the rule to start with:
lib_uninstall_library 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 lib_uninstall_library call is checked against it from then on.
Questions about lib_uninstall_library
Unregister a library from the environment's Available Libraries. 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 lib_uninstall_library: 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.
lib_uninstall_library 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 lib_uninstall_library 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 lib_uninstall_library. 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.
lib_uninstall_library 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