This record as markdown: /tools/io-github-dreamrec-livepilot/force-arrangement.md
What force_arrangement does on Livepilot
AI agents call force_arrangement to permanently remove resources in Livepilot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why force_arrangement is rated Critical
An AI agent that decides to call force_arrangement doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Livepilot is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs force_arrangement safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livepilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For force_arrangement, this is the rule to start with:
force_arrangement 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 Livepilot, apply this rule, and every force_arrangement call is checked against it from then on.
Questions about force_arrangement
force_arrangement is a destructive tool on the Livepilot MCP server. It is categorised as a Destructive tool in the Livepilot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Livepilot MCP server in PolicyLayer and add a rule for force_arrangement: 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 Livepilot. Nothing to install.
force_arrangement 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 force_arrangement 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 force_arrangement. 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.
force_arrangement is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livepilot, and thousands of servers like it.
Across the catalogue