inpaint_image
AI agents use inpaint_image 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.
Inpainting modifies images by filling in or editing specific regions—a reversible write operation. It does not delete data irreversibly (not Destructive), execute arbitrary code (not Execute), or involve financial transactions. The blast radius is medium since an agent could generate misleading or inappropriate modified images, but changes can be undone or reverted.
From the tool's definition Tool name 'inpaint_image' indicates image modification; sibling tools include 'generate_image', 'outpaint_image', 'remove_object', and 'remove_background' which all modify images.
Attacks that exploit this kind of access
inpaint_image. 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 inpaint_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 Bedrock Image. Nothing to install.
inpaint_image 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 inpaint_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 inpaint_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.
inpaint_image 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 →