filter-log-events
AI agents call filter-log-events to retrieve information from Amazon MQ MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name alone, 'filter-log-events' appears to query or retrieve log data from Amazon MQ brokers without modifying state. This is a read-only operation with no side effects. The empty description reduces confidence slightly, but the semantic meaning of 'filter' on 'log-events' strongly suggests data retrieval rather than modification or execution of arbitrary operations.
From the tool's definition Tool name 'filter-log-events' indicates log querying/retrieval. The description is empty, limiting certainty.
Attacks that exploit this kind of access
filter-log-events. It is categorised as a Read tool in the Amazon MQ MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for filter-log-events: 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 Amazon MQ MCP Server. Nothing to install.
filter-log-events 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 filter-log-events 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 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 Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.