Filter log events from CloudWatch Logs. Args: log_group_name: The name of the log group log_group_identifier: The unique identifier of the log group log_stream_names: Optional list of log stream names to search log_stream_name_prefix: Optional prefix to match log stream names ...
High parameter count (12 properties)
Part of the AWS ElastiCache MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke filter-log-events to trigger processes or run actions in AWS ElastiCache MCP Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
filter-log-events can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
filter-log-events:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full AWS ElastiCache MCP Server policy for all 39 tools.
Agents calling execute-class tools like filter-log-events have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
filter-log-events is one of the high-risk operations in AWS ElastiCache MCP Server. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Filter log events from CloudWatch Logs. Args: log_group_name: The name of the log group log_group_identifier: The unique identifier of the log group log_stream_names: Optional list of log stream names to search log_stream_name_prefix: Optional prefix to match log stream names start_time: The start of the time range, inclusive end_time: The end of the time range, inclusive filter_pattern: The filter pattern to use interleaved: If true, multiple log streams are interleaved unmask: If true, unmask sensitive log data starting_token: Token for getting the next set of events page_size: Number of events to return per page max_items: Maximum number of events to return in total Returns: Dict containing: - events: List of filtered log events - searchedLogStreams: List of log streams that were searched - nextToken: Token for getting the next set of events. It is categorised as a Execute tool in the AWS ElastiCache MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for filter-log-events. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS ElastiCache MCP Server MCP server.
filter-log-events 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 filter-log-events rule in your Intercept 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 Intercept policy for filter-log-events. 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.
filter-log-events is provided by the AWS ElastiCache MCP Server MCP server (awslabs.elasticache-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.