libi.drop_proxies

Delete preview proxies for every video on the piece to free disk space. Proxies regenerate on next edit session.

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.drop-proxies.md

WHAT IT DOES

What libi.drop_proxies does on Libi

AI agents call libi.drop_proxies 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.drop_proxies is rated Critical

Irreversibly deletes data (proxies) that cannot be recovered without regeneration, though impact is limited to cache artifacts.

From the tool's definition Delete preview proxies for every video on the piece to free disk space.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

libi.drop_proxies Hidden

libi.drop_proxies 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.drop_proxies"
  ]
}

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.drop_proxies call is checked against it from then on.

FAQ

Questions about libi.drop_proxies

What does the libi.drop_proxies tool do? +

Delete preview proxies for every video on the piece to free disk space. Proxies regenerate on next edit session. 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.drop_proxies? +

Register the Libi MCP server in PolicyLayer and add a rule for libi.drop_proxies: 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.drop_proxies? +

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

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

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

libi.drop_proxies 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 →