lib_remove_model

A destructive tool on the Eda Agent MCP server.

SERVEREda Agent SOURCEsalitronic/eda-agent

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/eda-agent/lib-remove-model.md

WHAT IT DOES

What lib_remove_model does on Eda Agent

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

RISK

Why lib_remove_model is rated Critical

Tool name suggests permanent removal of library models with no undo capability.

From the tool's definition uninformative description; lib_remove_model implies irreversible library deletion

Attacks that exploit this kind of access

RECOMMENDED RULE

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

lib_remove_model Hidden

lib_remove_model 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_remove_model"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Eda Agent, apply this rule, and every lib_remove_model call is checked against it from then on.

FAQ

Questions about lib_remove_model

What does the lib_remove_model tool do? +

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

How do I enforce a policy on lib_remove_model? +

Register the Eda Agent MCP server in PolicyLayer and add a rule for lib_remove_model: 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.

What risk level is lib_remove_model? +

lib_remove_model 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_remove_model? +

Yes. Add a rate_limit block to the lib_remove_model 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_remove_model completely? +

Set action: deny in the PolicyLayer policy for lib_remove_model. 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_remove_model? +

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

KEEP EXPLORING

More on Eda Agent, and thousands of servers like it.

This server

All 726 Eda Agent tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →