AI agents call filter-log-events to retrieve information from Amazon EKS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Log filtering operations are inherently read-only—they retrieve and query existing log data without altering, deleting, or executing anything. Even with an empty description, the name clearly indicates a data retrieval operation. Confidence is moderately high (0.75) because the lack of description introduces some uncertainty about edge cases, but the function name is unambiguous.
From the tool's definition Tool name 'filter-log-events' indicates log query/retrieval functionality. The empty description prevents confirmation of exact behavior, but the name strongly suggests filtering and reading log data without modification.
Documented attack patterns abuse exactly the kind of access filter-log-events gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon EKS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for filter-log-events:
{
"version": "1",
"default": "deny",
"tools": {
"filter-log-events": {}
}
}filter-log-events is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
filter-log-events. It is categorised as a Read tool in the Amazon EKS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon EKS 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 EKS 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 EKS MCP Server MCP server (awslabs.eks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon EKS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Amazon EKS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.