Install, uninstall, list, and discover LocalStack Extensions from the marketplace
AI agents invoke localstack-extensions to trigger actions in Localstack. 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 |
|---|---|---|---|
name | string | — | Extension package name (e.g. 'localstack-extension-typedb' or 'localstack-extension-typedb==1.0.0'). Required for install and uninstall actions. |
action | string | Yes | list = installed extensions; install = install an extension; uninstall = remove an extension; available = browse the marketplace/extensions library |
source | string | — | Git URL to install from (e.g. 'git+https://github.com/org/repo.git'). Use this instead of name when installing from a repository. |
Parameters from the server's own tool schema.
This tool can install and uninstall extensions, which involves executing package management operations on the LocalStack environment. Installing extensions runs arbitrary third-party code and modifying the runtime environment; uninstalling removes components.
From the tool's definition 'Install, uninstall, list, and discover LocalStack Extensions from the marketplace'
Attacks that exploit this kind of access
Install, uninstall, list, and discover LocalStack Extensions from the marketplace. It is categorised as a Execute tool in the Localstack MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
localstack-extensions accepts 3 parameters: name, action, source. 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-extensions: 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-extensions 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 localstack-extensions 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-extensions. 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-extensions 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 →