LocalStack log analyzer that helps developers quickly diagnose issues and understand their LocalStack interactions
AI agents call localstack-logs-analysis to retrieve information from Localstack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
lines | number | — | Number of recent log lines to fetch and analyze. |
filter | string | — | Raw keyword filter. Only used with 'logs' mode. |
service | string | — | Filter by AWS service (e.g., 's3', 'lambda'). Used with 'errors' and 'requests' modes. |
operation | string | — | Filter by a specific API operation (e.g., 'CreateBucket'). Requires 'service'. Used with 'requests' mode. |
analysisType | string | — | The analysis to perform: 'summary' (default), 'errors', 'requests', or 'logs' for raw output. |
Parameters from the server's own tool schema.
The tool reads and analyzes existing log data to help diagnose issues. This is a passive read/query operation with no side effects, modifications, or destructive actions. Severity is low as it only retrieves log information.
From the tool's definition log analyzer that helps developers quickly diagnose issues and understand their LocalStack interactions
Attacks that exploit this kind of access
LocalStack log analyzer that helps developers quickly diagnose issues and understand their LocalStack interactions. It is categorised as a Read tool in the Localstack MCP Server, which means it retrieves data without modifying state.
localstack-logs-analysis accepts 5 parameters: lines, filter, service, operation, analysisType. 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-logs-analysis: 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-logs-analysis is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the localstack-logs-analysis 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-logs-analysis. 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-logs-analysis 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 →