build_and_push_image_to_ecr

THE RISK

High Risk

Why build_and_push_image_to_ecr needs a policy

This tool executes external build and deployment processes whose effects depend on the code being built and image contents being pushed. While not destructive in isolation, it can execute arbitrary code during the build process and modify the ECR registry state.

From the tool's definition Tool name 'build_and_push_image_to_ecr' indicates execution of container image build operations and deployment to AWS Elastic Container Registry.

Documented attack patterns abuse exactly the kind of access build_and_push_image_to_ecr gives an agent:

POLICY

How to control build_and_push_image_to_ecr

PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Support MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for build_and_push_image_to_ecr:

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"
        }
      ]
    }
  }
}

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.

Create a free account and register AWS Support MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More AWS Support MCP Server tools

Destructive bulk_delete_by_criteria bulk_delete_by_criteria Destructive cache_delete Delete a value from the cache. Destructive cache_delete_many Delete multiple values from the cache. Destructive cache_delete_multi Delete multiple values from the cache (alias for delete_many). Destructive cancel_logs_insight_query cancel_logs_insight_query Destructive delete delete Destructive delete_access_key delete_access_key Destructive delete_agent_runtime delete_agent_runtime

All 805 AWS Support MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

Govern code and CI agents → Branch allowlists, approval on merges, and rate caps on the build and pipeline tools agents trigger.
High-risk tools in AWS Support MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

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 AWS Support MCP Server 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 AWS Support MCP Server 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 AWS Support MCP Server. 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 AWS Support MCP Server MCP server (awslabs.aws-support-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AWS Support MCP Server tool call.

Start from AWS Support MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →