libi.remove_effect

Delete a custom effect package by id.

SERVERLibi SOURCENagellabs/libi

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/libi/libi.remove-effect.md

WHAT IT DOES

What libi.remove_effect does on Libi

AI agents call libi.remove_effect to permanently remove resources in Libi, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why libi.remove_effect is rated Critical

Irreversibly deletes user-created effect packages; effects cannot be recovered after removal.

From the tool's definition Delete a custom effect package by id

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs libi.remove_effect safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Libi, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For libi.remove_effect, this is the rule to start with:

libi.remove_effect Hidden

libi.remove_effect 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": [
    "libi.remove_effect"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about libi.remove_effect

What does the libi.remove_effect tool do? +

Delete a custom effect package by id. It is categorised as a Destructive tool in the Libi 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 libi.remove_effect? +

Register the Libi MCP server in PolicyLayer and add a rule for libi.remove_effect: 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 Libi. Nothing to install.

What risk level is libi.remove_effect? +

libi.remove_effect 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 libi.remove_effect? +

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

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

libi.remove_effect is provided by the Libi MCP server (Nagellabs/libi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Libi, and thousands of servers like it.

This server

All 215 Libi tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →