build_and_push_image_to_ecr
AI agents invoke build_and_push_image_to_ecr to trigger actions in AWS Documentation 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.
This tool triggers external operations (Docker/container build and ECR push) whose effects depend on the image content and registry target. While not immediately destructive, it executes code and modifies remote state. The empty description lowers confidence slightly, but the name clearly indicates execution and side effects.
From the tool's definition Tool name 'build_and_push_image_to_ecr' indicates building container images and pushing them to AWS Elastic Container Registry, which involves executing build processes and external operations.
Documented attack patterns abuse exactly the kind of access build_and_push_image_to_ecr gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Documentation MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for build_and_push_image_to_ecr:
{
"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.
Free to start. No card required.
build_and_push_image_to_ecr. It is categorised as a Execute tool in the AWS Documentation MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS Documentation 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 Documentation MCP Server. Nothing to install.
build_and_push_image_to_ecr 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 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.
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.
build_and_push_image_to_ecr is provided by the AWS Documentation MCP Server MCP server (awslabs.aws-documentation-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Documentation 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 Documentation MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.