Configures LocalStack's IAM enforcement and analyzes logs to automatically generate missing IAM policies.
AI agents invoke localstack-iam-policy-analyzer 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 |
|---|---|---|---|
mode | string | — | The enforcement mode to set. This is required only when the action is 'set-mode'. |
action | string | Yes | The action to perform: 'set-mode' to configure enforcement, 'analyze-policies' to generate a policy from logs, or 'get-status' to check the current mode. |
Parameters from the server's own tool schema.
This tool both configures IAM enforcement settings (a Write/Execute action that changes security posture) and automatically generates IAM policies based on log analysis. Automatically generating and potentially applying IAM policies is an Execute-level action with high blast radius — misconfigured or overly permissive IAM policies could grant unintended access across the environment.
From the tool's definition 'Configures LocalStack's IAM enforcement and analyzes logs to automatically generate missing IAM policies'
Attacks that exploit this kind of access
Configures LocalStack's IAM enforcement and analyzes logs to automatically generate missing IAM policies. 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-iam-policy-analyzer accepts 2 parameters: mode, action. 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-iam-policy-analyzer: 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-iam-policy-analyzer 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-iam-policy-analyzer 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-iam-policy-analyzer. 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-iam-policy-analyzer 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 →