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

libi.attach_storyboard_keyframe

Attach a generated Tier-2 keyframe image (by libi file id) to a storyboard card, recording its cost and advancing the card to the keyframe stage. The agent generates the image (gpt-image-2, conditioned on the card

SERVERLibi SOURCENagellabs/libi
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/libi/libi.attach-storyboard-keyframe.md

What libi.attach_storyboard_keyframe does on Libi

AI agents use libi.attach_storyboard_keyframe to create or update resources in Libi, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Libi environment.

Why libi.attach_storyboard_keyframe is rated Medium

Creates and modifies storyboard state reversibly; records cost tracking but does not execute external operations or move funds.

From the tool's definition Attach keyframe image to storyboard card, recording cost, advancing card stage

Questions about libi.attach_storyboard_keyframe

What does the libi.attach_storyboard_keyframe tool do? +

Attach a generated Tier-2 keyframe image (by libi file id) to a storyboard card, recording its cost and advancing the card to the keyframe stage. The agent generates the image (gpt-image-2, conditioned on the card. It is categorised as a Write tool in the Libi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on libi.attach_storyboard_keyframe? +

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

libi.attach_storyboard_keyframe is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit libi.attach_storyboard_keyframe? +

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

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

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

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