fleets_startInstance
Start already admitted Henry compute (POST /v1/fleets/instances/{instance_id}/start) [service status: unverified]
This record as markdown: /tools/lifesi-genesis-mcp/fleets-startinstance.md
What fleets_startInstance does on Genesis
AI agents invoke fleets_startInstance to trigger actions in Genesis. 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 |
|---|---|---|---|
instance_id | string | Yes | |
idempotency_key | string | — | Optional canonical UUID4 for this explicit operation; retain it after an uncertain reply. Carries no authority. |
Parameters from the server's own tool schema.
Why fleets_startInstance is rated High
fleets_startInstance triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs fleets_startInstance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fleets_startInstance, this is the rule to start with:
fleets_startInstance 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 Genesis, apply this rule, and every fleets_startInstance call is checked against it from then on.
Questions about fleets_startInstance
Start already admitted Henry compute (POST /v1/fleets/instances/{instance_id}/start) [service status: unverified]. It is categorised as a Execute tool in the Genesis MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
fleets_startInstance accepts 2 parameters: instance_id, idempotency_key. Required: instance_id. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for fleets_startInstance: 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 Genesis. Nothing to install.
fleets_startInstance 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 fleets_startInstance 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 fleets_startInstance. 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.
fleets_startInstance is provided by the Genesis MCP server (@lifesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genesis, and thousands of servers like it.
Across the catalogue