New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

libi.analysis_remove_step

Delete an analysis step row (and any cascaded keyframes if kind=frames). Use to fully clear and redo a step.

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.analysis-remove-step.md

What libi.analysis_remove_step does on Libi

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

Why libi.analysis_remove_step is rated Critical

Irreversibly deletes analysis steps and associated keyframes in video composition workflow.

From the tool's definition Delete an analysis step row and any cascaded keyframes; fully clear and redo a step.

Questions about libi.analysis_remove_step

What does the libi.analysis_remove_step tool do? +

Delete an analysis step row (and any cascaded keyframes if kind=frames). Use to fully clear and redo a step. 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.analysis_remove_step? +

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

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

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

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

libi.analysis_remove_step 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.

More on Libi, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Libi's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.