AI agents invoke CloneContainerToECR to trigger actions in AWS AppSync 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 suggests cloning a container image to Amazon ECR (Elastic Container Registry), which involves pulling a container image and pushing it to a registry. This is an Execute/Write operation with potentially high impact (pushing images to a container registry could affect deployments). However, the empty description reduces confidence significantly.
From the tool's definition Tool name: CloneContainerToECR — description is empty and uninformative
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 AWS AppSync 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 AWS AppSync MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS AppSync 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 AWS AppSync 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 AWS AppSync MCP Server MCP server (awslabs.aws-appsync-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS AppSync 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 AWS AppSync MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.