AI agents call esm_msk_policy as a supporting operation in Amazon EKS MCP Server workflows.
The description is empty, making it impossible to determine the tool's actual behavior. The name suggests something related to MSK (Amazon Managed Streaming for Kafka) policy configuration, which could be a Write or Execute action, but without confirmation, confidence is very low. Defaulting to Other given the ambiguity, while noting medium severity due to the potential policy-manipulation implications of the name.
From the tool's definition Tool name 'esm_msk_policy' and empty description provide no meaningful information about what the tool does.
Documented attack patterns abuse exactly the kind of access esm_msk_policy 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 esm_msk_policy:
{
"version": "1",
"default": "deny",
"tools": {
"esm_msk_policy": {
"limits": [
{
"counter": "esm_msk_policy_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} esm_msk_policy gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
esm_msk_policy. It is categorised as a Other tool in the Amazon EKS MCP Server MCP Server, which means it performs auxiliary operations.
Register the Amazon EKS MCP Server MCP server in PolicyLayer and add a rule for esm_msk_policy: 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.
esm_msk_policy is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the esm_msk_policy 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 esm_msk_policy. 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.
esm_msk_policy 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.