Manages remote LocalStack Cloud Pods with following actions: save, load, delete
AI agents call localstack-cloud-pods 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 |
|---|---|---|---|
action | string | Yes | The Cloud Pods action to perform. |
pod_name | string | — | The name of the Cloud Pod. This is required for 'save', 'load', and 'delete' actions. |
Parameters from the server's own tool schema.
While the tool also offers reversible operations (save, load), the presence of 'delete' as a core action makes it Destructive—this category takes precedence when a tool can perform irreversible data removal. Deleting a Cloud Pod cannot be undone and removes infrastructure state.
From the tool's definition Tool description explicitly includes 'delete' as one of the supported actions for managing LocalStack Cloud Pods. The delete action irreversibly removes cloud pod data/state.
Attacks that exploit this kind of access
Manages remote LocalStack Cloud Pods with following actions: save, load, 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-cloud-pods accepts 2 parameters: action, pod_name. 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-cloud-pods: 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-cloud-pods 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-cloud-pods 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-cloud-pods. 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-cloud-pods 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 →