create_ellipse_mask
AI agents use create_ellipse_mask to create or update resources in Bedrock Image — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bedrock Image environment.
Mask creation is a Write operation—it generates new structured data (a mask) that modifies subsequent image processing steps. It is reversible (can be discarded or replaced) and has no permanent destructive effects. The empty description lowers confidence slightly, but the naming pattern and sibling tools clearly indicate this is part of an image editing workflow.
From the tool's definition Tool name 'create_ellipse_mask' indicates creation of a mask object. Sibling tools on this server (create_full_mask, create_rectangular_mask, inpaint_image, outpaint_image, remove_background) are image editing operations that create or modify image data.
Attacks that exploit this kind of access
create_ellipse_mask. It is categorised as a Write tool in the Bedrock Image MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bedrock Image MCP server in PolicyLayer and add a rule for create_ellipse_mask: 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 Bedrock Image. Nothing to install.
create_ellipse_mask is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_ellipse_mask 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 create_ellipse_mask. 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.
create_ellipse_mask is provided by the Bedrock Image MCP server (kalleeh/bedrock-image-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →