AI agents call get_eks_vpc_config to retrieve information from Amazon Redshift MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves VPC configuration data without modifying it. Although the description is empty (lowering confidence slightly), the name strongly indicates a read operation. Medium severity applies because VPC configuration details could inform network reconnaissance or privilege escalation attacks if misused by an unauthorized agent, but it is fundamentally a read operation with no direct destructive capability.
From the tool's definition Tool name 'get_eks_vpc_config' indicates retrieval of VPC configuration for EKS clusters. The 'get_' prefix and absence of mutation language suggests read-only data retrieval.
Documented attack patterns abuse exactly the kind of access get_eks_vpc_config gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Redshift MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_eks_vpc_config:
{
"version": "1",
"default": "deny",
"tools": {
"get_eks_vpc_config": {}
}
} get_eks_vpc_config 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.
get_eks_vpc_config. It is categorised as a Read tool in the Amazon Redshift MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon Redshift MCP Server MCP server in PolicyLayer and add a rule for get_eks_vpc_config: 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 Redshift MCP Server. Nothing to install.
get_eks_vpc_config 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 get_eks_vpc_config 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 get_eks_vpc_config. 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.
get_eks_vpc_config is provided by the Amazon Redshift MCP Server MCP server (awslabs.redshift-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon Redshift 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 Redshift MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.