Manage cloud-hosted LocalStack Ephemeral Instances: create, list, fetch logs, and delete.
AI agents call localstack-ephemeral-instances to permanently remove resources in Localstack — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Instance name. Required for create, logs, and delete actions. |
action | string | Yes | The Ephemeral Instances action to perform. |
envVars | object | — | Additional environment variables to pass to the ephemeral instance (create action only), translated to repeated --env KEY=VALUE flags. |
cloudPod | string | — | Optional Cloud Pod name to initialize state for create action. This is passed as CLOUD_POD_NAME. |
lifetime | number | — | Lifetime in minutes for create action. Defaults to CLI default when omitted. |
extension | string | — | Optional extension package to preload for create action. This is passed as EXTENSION_AUTO_INSTALL. |
Parameters from the server's own tool schema.
Although the tool also includes reversible operations (create, list, fetch logs), the 'delete' action falls under Destructive category. Per the classification rules, when a tool spans multiple categories, the most severe applicable category is chosen. Destructive ranks higher than Write.
From the tool's definition Tool description explicitly includes 'delete' action on LocalStack Ephemeral Instances, which irreversibly removes instances and associated cloud-hosted resources.
Attacks that exploit this kind of access
Manage cloud-hosted LocalStack Ephemeral Instances: create, list, fetch logs, and delete. It is categorised as a Destructive tool in the Localstack MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
localstack-ephemeral-instances accepts 6 parameters: name, action, envVars, cloudPod, lifetime, extension. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Localstack MCP server in PolicyLayer and add a rule for localstack-ephemeral-instances: 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 Localstack. Nothing to install.
localstack-ephemeral-instances 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 localstack-ephemeral-instances 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 localstack-ephemeral-instances. 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.
localstack-ephemeral-instances is provided by the Localstack MCP server (@localstack/localstack-mcp-server). 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 →