This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/fly-create-machine.md
What fly_create_machine does on UnClick
AI agents invoke fly_create_machine to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
env | string | — | JSON object of environment variables |
image | string | Yes | Docker image to run (e.g. nginx:latest) |
api_key | string | — | |
app_name | string | Yes | |
machine_name | string | — | Optional machine name |
Parameters from the server's own tool schema.
Why fly_create_machine is rated High
This tool provisions and starts a new compute machine (VM) on Fly.io. Spinning up machines incurs resource usage and potential cost, and executes infrastructure-level operations. It is not merely writing data — it triggers real compute resources. Financial implications are secondary/indirect, so Execute is the most appropriate primary category with high severity due to potential runaway resource provisioning.
From the tool's definition Create a new machine in a Fly.io app
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs fly_create_machine 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_create_machine, this is the rule to start with:
fly_create_machine stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_create_machine call is checked against it from then on.
Questions about fly_create_machine
Create a new machine in a Fly.io app. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
fly_create_machine accepts 5 parameters: env, image, api_key, app_name, machine_name. Required: image, 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_create_machine: 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_create_machine is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the fly_create_machine 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_create_machine. 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_create_machine 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.
Across the catalogue