This record as markdown: /tools/aws/finch-push-image.md
What finch_push_image does on AWS
AI agents invoke finch_push_image to trigger actions in AWS. 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 finch_push_image is rated High
The name suggests pushing a container image (likely via Finch, an AWS container tool) to a registry. This is an external operation that modifies a remote registry. However, the description is empty, so confidence is reduced. Pushing an image is a Write/Execute operation — it triggers an external operation on a registry.
From the tool's definition Tool name 'finch_push_image' — 'push_image' suggests pushing a container image to a registry, which is an external operation with side effects.
Attacks that exploit this kind of access
The rule that runs finch_push_image safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For finch_push_image, this is the rule to start with:
finch_push_image 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.
The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every finch_push_image call is checked against it from then on.
Questions about finch_push_image
finch_push_image is a execute tool on the AWS MCP server. It is categorised as a Execute tool in the AWS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS MCP server in PolicyLayer and add a rule for finch_push_image: 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. Nothing to install.
finch_push_image 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 finch_push_image 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 finch_push_image. 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.
finch_push_image is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AWS, and thousands of servers like it.
This server
Across the catalogue