Manage persistent volumes & file storages: list/create/update/delete for applications, databases, services
AI agents call storages to permanently remove resources in Coolify — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While the tool encompasses read (list), write (create/update), and execute operations, the inclusion of 'delete' for persistent storage elevates this to Destructive category per classification rules. Deleting persistent volumes or file storages is irreversible and represents the highest-severity capability.
From the tool's definition Tool description explicitly includes 'delete' operations on persistent volumes and file storages. This enables irreversible removal of data that cannot be undone.
Attacks that exploit this kind of access
Manage persistent volumes & file storages: list/create/update/delete for applications, databases, services. It is categorised as a Destructive tool in the Coolify MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Coolify MCP server in PolicyLayer and add a rule for storages: 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 Coolify. Nothing to install.
storages 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 storages 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 storages. 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.
storages is provided by the Coolify MCP server (jurislm/coolify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →