libi.analysis_remove_step
Delete an analysis step row (and any cascaded keyframes if kind=frames). Use to fully clear and redo a step.
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.
Attacks that exploit this kind of access
The rule that runs libi.analysis_remove_step 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.analysis_remove_step, this is the rule to start with:
libi.analysis_remove_step 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 Libi, apply this rule, and every libi.analysis_remove_step call is checked against it from then on.
Questions about libi.analysis_remove_step
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.
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.
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.
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.
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.
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.
Across the catalogue