This record as markdown: /tools/libi/libi.set-complexity-mode.md
What libi.set_complexity_mode does on Libi
AI agents use libi.set_complexity_mode 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.set_complexity_mode is rated Medium
Modifies overlay state which is reversible; affects video composition but not destructively.
From the tool's definition Switch a SPECIFIC overlay
Attacks that exploit this kind of access
The rule that runs libi.set_complexity_mode 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.set_complexity_mode, this is the rule to start with:
libi.set_complexity_mode 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.set_complexity_mode call is checked against it from then on.
Questions about libi.set_complexity_mode
Switch a SPECIFIC overlay. 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.set_complexity_mode: 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.set_complexity_mode 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.set_complexity_mode 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.set_complexity_mode. 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.set_complexity_mode 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