libi.save_asset
Save a generated asset (audio, image, etc.) for the current piece. Stores the file and registers it in the database so it can be referenced in scene draw functions.
This record as markdown: /tools/libi/libi.save-asset.md
What libi.save_asset does on Libi
AI agents use libi.save_asset 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.save_asset is rated Medium
Creates and stores generated media assets reversibly; modification or deletion possible later.
From the tool's definition Save, stores file, registers database
Attacks that exploit this kind of access
The rule that runs libi.save_asset 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.save_asset, this is the rule to start with:
libi.save_asset stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Libi, apply this rule, and every libi.save_asset call is checked against it from then on.
Questions about libi.save_asset
Save a generated asset (audio, image, etc.) for the current piece. Stores the file and registers it in the database so it can be referenced in scene draw functions. 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.
Register the Libi MCP server in PolicyLayer and add a rule for libi.save_asset: 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.save_asset is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the libi.save_asset 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.save_asset. 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.save_asset 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.
This server
Across the catalogue