AI agents invoke CloneContainerToECR to trigger actions in Amazon Redshift MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The name implies an operation that clones a container image and pushes it to ECR, which is an external execution/write operation with potential security implications (introducing images into a container registry). However, the description is empty, so confidence is reduced. The most severe applicable category is Execute, as it triggers an external cloud operation.
From the tool's definition Tool name 'CloneContainerToECR' suggests copying/cloning a container image to Amazon ECR (Elastic Container Registry), which triggers an external operation affecting cloud infrastructure.
Documented attack patterns abuse exactly the kind of access CloneContainerToECR 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 CloneContainerToECR:
{
"version": "1",
"default": "deny",
"tools": {
"CloneContainerToECR": {
"limits": [
{
"counter": "clonecontainertoecr_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}CloneContainerToECR stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
CloneContainerToECR. It is categorised as a Execute tool in the Amazon Redshift MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Amazon Redshift MCP Server MCP server in PolicyLayer and add a rule for CloneContainerToECR: 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.
CloneContainerToECR 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 CloneContainerToECR 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 CloneContainerToECR. 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.
CloneContainerToECR 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.