# list_application_storages

List all persistent and file storages for an application.

Agent View of the PolicyLayer registry record for `list_application_storages`. HTML page: https://policylayer.com/tools/coolify/list-application-storages

## Facts

- Tool: `list_application_storages`
- Server: Coolify (`coolify-mcp-server`) — https://policylayer.com/tools/coolify.md
- Install: `npx -y coolify-mcp-server`
- Homepage: git+https://github.com/wrediam/coolify-mcp-server.git
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_application_storages",
    "arguments": {}
  }
}
```

## Why list_application_storages is rated Low

This tool queries and retrieves information about storage resources associated with an application. It has no side effects, does not modify data, execute code, delete resources, or involve financial transactions. It is a straightforward data retrieval operation typical of Read category tools.

From the tool's own definition: "Tool name includes 'list' and description states 'List all persistent and file storages for an application.' The verb 'list' and the action of retrieving storage information without modification indicate a read-only query operation."

## Use case

AI agents call list_application_storages to retrieve information from Coolify without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Coolify:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_application_storages": {}
  }
}
```

## Other tools on Coolify (110)

- `delete_application` — Destructive — https://policylayer.com/tools/coolify/delete-application.md
- `delete_application_env` — Destructive — https://policylayer.com/tools/coolify/delete-application-env.md
- `delete_application_scheduled_task` — Destructive — https://policylayer.com/tools/coolify/delete-application-scheduled-task.md
- `delete_application_storage` — Destructive — https://policylayer.com/tools/coolify/delete-application-storage.md
- `delete_cloud_token` — Destructive — https://policylayer.com/tools/coolify/delete-cloud-token.md
- `delete_database` — Destructive — https://policylayer.com/tools/coolify/delete-database.md
- `delete_database_env` — Destructive — https://policylayer.com/tools/coolify/delete-database-env.md
- `delete_environment` — Destructive — https://policylayer.com/tools/coolify/delete-environment.md
- `delete_github_app` — Destructive — https://policylayer.com/tools/coolify/delete-github-app.md
- `delete_private_key` — Destructive — https://policylayer.com/tools/coolify/delete-private-key.md
- `delete_project` — Destructive — https://policylayer.com/tools/coolify/delete-project.md
- `delete_server` — Destructive — https://policylayer.com/tools/coolify/delete-server.md
- `delete_service` — Destructive — https://policylayer.com/tools/coolify/delete-service.md
- `delete_service_env` — Destructive — https://policylayer.com/tools/coolify/delete-service-env.md
- `delete_service_scheduled_task` — Destructive — https://policylayer.com/tools/coolify/delete-service-scheduled-task.md
- `disable_api` — Destructive — https://policylayer.com/tools/coolify/disable-api.md
- `cancel_deployment` — Execute — https://policylayer.com/tools/coolify/cancel-deployment.md
- `deploy_by_tag_or_uuid` — Execute — https://policylayer.com/tools/coolify/deploy-by-tag-or-uuid.md
- `enable_api` — Execute — https://policylayer.com/tools/coolify/enable-api.md
- `restart_application` — Execute — https://policylayer.com/tools/coolify/restart-application.md
- `restart_database` — Execute — https://policylayer.com/tools/coolify/restart-database.md
- `restart_service` — Execute — https://policylayer.com/tools/coolify/restart-service.md
- `start_application` — Execute — https://policylayer.com/tools/coolify/start-application.md
- `start_database` — Execute — https://policylayer.com/tools/coolify/start-database.md
- `start_service` — Execute — https://policylayer.com/tools/coolify/start-service.md
- `stop_application` — Execute — https://policylayer.com/tools/coolify/stop-application.md
- `stop_database` — Execute — https://policylayer.com/tools/coolify/stop-database.md
- `stop_service` — Execute — https://policylayer.com/tools/coolify/stop-service.md
- `get_application` — Read — https://policylayer.com/tools/coolify/get-application.md
- `get_application_logs` — Read — https://policylayer.com/tools/coolify/get-application-logs.md
- …and 80 more: https://policylayer.com/tools/coolify.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=coolify · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/coolify