This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/fly-list-volumes.md
What fly_list_volumes does on UnClick
AI agents call fly_list_volumes to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | — | |
app_name | string | Yes |
Parameters from the server's own tool schema.
Why fly_list_volumes is rated Low
This tool retrieves information about volumes attached to a Fly.io app without side effects. It is a read-only query operation that does not create, modify, delete, or execute code. The blast radius if misused by an AI agent is minimal—an attacker gains visibility into infrastructure but cannot alter it or trigger actions.
From the tool's definition Tool name and description indicate a list operation: 'fly_list_volumes' lists volumes. No modification, deletion, or execution of external operations occurs.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs fly_list_volumes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fly_list_volumes, this is the rule to start with:
fly_list_volumes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every fly_list_volumes call is checked against it from then on.
Questions about fly_list_volumes
List all volumes attached to a Fly.io app. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
fly_list_volumes accepts 2 parameters: api_key, app_name. Required: app_name. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for fly_list_volumes: 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 UnClick. Nothing to install.
fly_list_volumes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fly_list_volumes 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 fly_list_volumes. 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.
fly_list_volumes is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue