Export, import, reset, and inspect LocalStack state using local file-based workflows on disk.
AI agents call localstack-state-management 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 local LocalStack state action to perform through the LocalStack State REST API. Use this tool for file-based state export/import workflows on disk. Use Clou |
services | object | — | Optional AWS service names for service-level granularity, such as ['s3', 'lambda'] or 's3,lambda'. Supported for export, reset, and inspect. Import restores the |
file_path | string | — | Local file path for state export or import. Required for import. For export, defaults to ls-state-export in the MCP server working directory if omitted. |
Parameters from the server's own tool schema.
The tool includes a 'reset' operation which irreversibly wipes LocalStack state, and an 'import' which overwrites existing state. These destructive/overwrite operations dominate the classification. A misuse could wipe all emulated AWS service state in a LocalStack environment, which is not recoverable without a prior export.
From the tool's definition 'reset' and 'import' operations in 'Export, import, reset, and inspect LocalStack state'
Risk signalsAccepts file system path (file_path)
Attacks that exploit this kind of access
Export, import, reset, and inspect LocalStack state using local file-based workflows on disk. 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-state-management accepts 3 parameters: action, services, file_path. 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-state-management: 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-state-management 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-state-management 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-state-management. 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-state-management 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 →