Injects, manages, and clears chaos faults and network effects in LocalStack to test system resilience.
AI agents invoke localstack-chaos-injector 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 |
|---|---|---|---|
rules | array | — | An array of fault rules. Required for 'inject-faults', 'add-fault-rule', and 'remove-fault-rule' actions. |
action | string | Yes | The specific chaos engineering action to perform. |
latency_ms | number | — | Network latency in milliseconds. Required for the 'inject-latency' action. |
Parameters from the server's own tool schema.
This tool actively injects chaos faults and network effects into a running LocalStack environment, which constitutes triggering external operations with potentially wide-ranging side effects.
From the tool's definition "Injects, manages, and clears chaos faults and network effects in LocalStack"
Risk signalsAccepts freeform code/query input (rules[].error.code) · High parameter count (10 properties)
Attacks that exploit this kind of access
Injects, manages, and clears chaos faults and network effects in LocalStack to test system resilience. 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-chaos-injector accepts 3 parameters: rules, action, latency_ms. 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-chaos-injector: 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-chaos-injector 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-chaos-injector 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-chaos-injector. 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-chaos-injector 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 →