CloneContainerToECR
AI agents invoke CloneContainerToECR to trigger actions in AWS IoT SiteWise 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 tool name implies an operation that copies/clones a container image and pushes it to ECR, which involves executing an external operation (registry push/write). This spans Write and Execute categories; Execute is chosen as it triggers an external operation. Confidence is low because the description is empty, leaving the exact behavior uncertain.
From the tool's definition Tool name 'CloneContainerToECR' suggests cloning a container image and pushing it to Amazon ECR (Elastic Container Registry)
Attacks that exploit this kind of access
CloneContainerToECR. It is categorised as a Execute tool in the AWS IoT SiteWise MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS IoT SiteWise 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 IoT SiteWise 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 IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.