build_and_push_image_to_ecr · Awslabs Valkey MCP

WHAT IT DOES

What build_and_push_image_to_ecr does on Awslabs Valkey

AI agents invoke build_and_push_image_to_ecr to trigger actions in Awslabs Valkey. 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.

WHY IT NEEDS A POLICY

Why build_and_push_image_to_ecr needs a policy

Building and pushing images to ECR executes external operations (Docker build, ECR push) whose effects depend on the image content and ECR repository state. While it involves writing to a registry, the primary action is executing a build process, making it Execute rather than Write. The blast radius is high because a malicious image pushed to ECR could compromise any service pulling from that registry.

From the tool's definition Tool name 'build_and_push_image_to_ecr' indicates building a container image and pushing it to Amazon ECR (Elastic Container Registry). This involves executing a build process and performing a write operation to a container registry.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

build_and_push_image_to_ecr Rate-limited

build_and_push_image_to_ecr 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "build_and_push_image_to_ecr": {
      "limits": [
        {
          "counter": "build_and_push_image_to_ecr_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Awslabs Valkey, so you can run agents against it safely.

FAQ

Questions about build_and_push_image_to_ecr

What does the build_and_push_image_to_ecr tool do? +

build_and_push_image_to_ecr. It is categorised as a Execute tool in the Awslabs Valkey MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on build_and_push_image_to_ecr? +

Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for build_and_push_image_to_ecr: 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 Awslabs Valkey. Nothing to install.

What risk level is build_and_push_image_to_ecr? +

build_and_push_image_to_ecr is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit build_and_push_image_to_ecr? +

Yes. Add a rate_limit block to the build_and_push_image_to_ecr 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.

How do I block build_and_push_image_to_ecr completely? +

Set action: deny in the PolicyLayer policy for build_and_push_image_to_ecr. 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.

What MCP server provides build_and_push_image_to_ecr? +

build_and_push_image_to_ecr is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.